Re: Raw socket based load balancing

We are soon writing a custom connector that will handle the setup, flow, and teardown. 

This connector will be spread across several servers located behind the load balancers.

Are the protocol details important for the load balancer? We'd ideally like to be able to just forward the tcp port through to the real server as a raw socket connection without any regard to its contents.

Regards,

Chris

----- Original Message -----
From: [email protected] <[email protected]>
To: Load Balancing Mailing List <[email protected]>
Sent: Wed Nov 18 13:13:00 2009
Subject: Re: [load balancing] Raw socket based load balancing

Any more specifics on the protocol?  What’s the connection setup, flow and teardown.  What’s the payload format?

 

KJ (Ken) Salchow, Jr. | Manager, Technical Marketing

	
D 651.423.1133

	M 612.868.1258

	P 206.272.5555

	F 206.272.5555

	www.f5.com <http://www.f5.com/> 

	

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Chris Kirby
Sent: Wednesday, November 18, 2009 11:54 AM
To: [email protected]
Subject: [load balancing] Raw socket based load balancing

 

 

We are currently using a pound/haproxy combination to load balancing incoming http/https connections.

 

We however have an upcoming requirement to load balance incoming raw socket connections with a proprietary protocol. I don't think pound/haproxy will work for this since they are proxy servers and is therefore drive by standard protocols.

 

Does anyone have any other recommendations on what open source load balancing apps we could use?  We may require session persistence as well (yet to be determined).

 

Regards,

 

Chri

_______________________________________________
lb-l mailing list
[email protected]
http://vegan.net/mailman/listinfo/lb-l
Searchable Archive: http://vegan.net/lb/archive
http://lbdigest.com Load Balancing Digest
http://lbwiki.com Load Balancing Wiki