Hi,
we have a bit of an issue with TCP handling in SER 2.0. It appears that dead connections cause the executing TCP process to hang for a short while until it figures things out. Too many such requests and processing essentially stops.
Now, I understand all of this has been fixed in SER 2.1 and all our problems will go away. Question is: Will we get new ones by upgrading. Or asked differently: Is there any experience with SER 2.1 and its statbility in a real world scenario? The boxes in question are edge proxies, so there is not much processing to be done other than basic forwarding and a bit of NAT handling. Can we risk it?
Best regards, Martin
Martin Hoffmann wrote:
Hi,
we have a bit of an issue with TCP handling in SER 2.0. It appears that dead connections cause the executing TCP process to hang for a short while until it figures things out. Too many such requests and processing essentially stops.
Now, I understand all of this has been fixed in SER 2.1 and all our problems will go away. Question is: Will we get new ones by upgrading. Or asked differently: Is there any experience with SER 2.1 and its statbility in a real world scenario? The boxes in question are edge proxies, so there is not much processing to be done other than basic forwarding and a bit of NAT handling. Can we risk it?
I think it is worth trying. We have been running it on iptel.org for quite a while. There has been one hard-to-reproduce mysql-lib crash and one hard-to-reproduce race-condition somewhere in TM (possibly on 2.0 too). The key part, TCP, should indeed justify an upgrade in your case.
-jiri
Best regards, Martin _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Jiri Kuthan -
Martin Hoffmann