Hello, ok Very good. Note that this flag is ignored if the backup function is stopped, so there is no need to clear the flag when switching to master mode. Regards -- Julian Anastasov <ja@xxxxxx> ___
Hello, It would be more right to add German Myzovsky <lawyer@xxxxxxxxx> as the tester. I'm just the coordinator. Yes, slave balancers set this flag to 1. In the case of a cluster fail-over the newly
Hello, Yes, I'll do it in the next days. Regards -- Julian Anastasov <ja@xxxxxx> _______________________________________________ Please read the documentation before posting - it's available at: http
Hello, Thank you very much! It's about ten days since we started to use on our servers kernel 3.8.0-28 (now 3.8.1-30) with your patch applied. So far, there are no signs of SYN spiraling or other pro
Hello, That is what I have implemented. I hope you will find a way to test it and after your feedback and comments from others we will post this patch for kernel inclusion. This is the link of the pa
Hello, I'd like to return to the discussion (some excerpts are below) to get some ideas on how we can plan development of our product in regards to IPVS development. Can we expect that the synchroniz
Hello, We tried to run with persistence but this made the situation even worse: after successfully accepting a connection from the client IP, a new (now from a different source port) should be handle
Hello, If connection still exists in balancer A it is not going to select new real server. May be only if expire_nodest_conn is set and when current real server becomes unavailable a new real server
Dear Graeme, We have this in place already, and in our case it does not work. It seems we have spurious packets somewhere in the system that trigger the packet flood. Note - the flood does not escala
Hi I documented this some time ago on this list, but will offer the solution that I came up with at the time - which coincidentally I gave to you as a possible solution to a separate problem you were
Dear Dmitry, So do we. We see intermittent loops of traffic, at various "levels", i.e. 15 Mbps if only one incoming packet gets duplicated, 30 Mbps if two are, etc. These storms die down on their own
Hello, We have met a quite troublesome situation which causes an internal SYN storm. The simplified version of the configuration consists of 2 servers - A and B, both running Linux kernel 3.7.4-20. B