clustering and session persistence

GarrettMackey

Hi

I'm reading the clustering.pdf document and I have some questions in relation to option 2.B.1.1 titled: Servers behind load balanacer.

1. How is the control_link_machine_name transmitted to the client via cookie?
2. Is the any other way of configuring lightstreamer to provide particular lightstreamer server instance details back to the client to aid with CR control and rebind connections.

We have a large environment with many lightstreamer instances behind a Load balancer and are seeing some issues regarding control and rebind attempts. Up to now we have relied on Load balancer stickiness for persistence but are looking at alternatives due to these rebind issues.

Any help appreciated.

Thanks
Garrett

Mone

Hi,

1. How is the control_link_machine_name transmitted to the client via cookie?

no we don't use cookies, the control link is sent back as part of our protocol

2. Is the any other way of configuring lightstreamer to provide particular lightstreamer server instance details back to the client to aid with CR control and rebind connections.

can you please make an example? What would you like to do? (let's see if we can help)

GarrettMackey

Hi Mone

Thanks for the response, in our environment we have dual site strategy with a global load balancer sitting in front. Each site has local load balanacer stickiness configured however it turns out there were issue configuring skickiness on the global load balancer level and networks guys were looking for something we could set in the app that would tell them which server/site the session originated. They have since come up with a network workaround.

Thanks
Garrett