Hi, On Sat, Oct 24, 2009 at 12:41:39AM +0200, XANi wrote: (...) > > As all the 16 messages are sent on the same connection (Connection is > > made only once in the TCP Client), the HAProxy is not re routing the > > remaining message to another node. > > > > Is this scenario achievable through HAProxy? > > > > And my next query is that, as I mentioned that my Client creates only > > one Connection and sends Business oriented logical messages, for the > > rest of the life time of the client, and can that traffic be load > > balanced? > > > > > > > > Eagerly waiting for your reply with comments and solutions if > > applicable. > AFAIK collectd knows nothing about whats goin on inside non-HTTP TCP > connections (it doesn't know if next packet is another "request"), for > that to work you would have to use one-transation-per-connection or > do heavy rewrite of haproxy to support your application protocol.
Exacly. As Mariusz explains it, there is no way to know what part of your stream may be extracted and sent anywhere else. TCP does not transport messages, it transports a continuous stream. If you use it for messages, it means you have a specific protocol for this. You could very well try to implement support for it into haproxy, but it could take some energy and will only push the problem one bit further and never solve the issue completely, because from your description, I understand that the client does not correctly cope with transmission errors. Regards, Willy
