Re: problem: beanstalk client with dynamic ip

[Andre Ruiz]

I have temporarily solved this problem making a vpn between the client and the server, so that the IPs of each end of the connection never change, even if the dynamic ip changes and the vpn reconnect.

But I still would be interested in knowing if this is an expected behaviour of the protocol.

Thanks,
Andre

[赵绪]

I want to sync data from mysql in IDC1 o mysql in IDC2. how to do ?

[Zhu Han]

This is the expected behavior of TCP/IP. When no data is sent over the wire, TCP can not detect the connection is broken after the IP is changed.

The only option is set SO_TIMEOUT on the connection to beanstalkd. Usually, you can set it larger than the timeout value of reserve operation, so the connection is not timed out prematurely.

best regards,
韩竹(Zhu Han)

坚果云, 最简捷易用的云存储
无限空间, 文件同步, 备份和分享!

Andre

--
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.

To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/no6kRRwdbZ8J.

To post to this group, send email to beansta...@googlegroups.com.
To unsubscribe from this group, send email to beanstalk-tal...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.

[Andre Ruiz]

Hi Zhu Han!

Thank you for answering.

I understand this is expected behaviour of tcp/ip, what I didn't know
is if this is intended behaviour of beanstalk clients. I could't find
any references on setting so_timeout on pheanstalk, I'll keep looking.
I guess the protocol or the clients should have a bultin protection
for that, it seems fragile for when client and server are distant over
the internet.

Thanks!
Andre

--
Andre Ruiz <andre...@gmail.com>
Curitiba, PR, Brasil
Tel +55 (41) 8407-3847