Forum Discussion
How To Change To Previous Node Despite Persistence
We have an application that uses three servers in a Load Balancing Pool. And, we run with no persistence since the application requires that we switch Nodes with each request. I know that sounds strange, but it's the way the App Developers need it.
But, in certain situations, the application needs to send the request to the previously selected node. Specifically, when the application does inquiries (GETs) it needs to always change nodes, but when it does updates (POSTs) it needs to stay with the previously selected node.
I do have an iRule set up to select a specific node, but the tricky part is to figure out what the last selected node was. To do this, I set up a Cookie that would track the Node Selected. The challenge is that the client isn't a Web Browser, it's a Java application. I was hoping the application developer could program in to read the Cookie and send it back. So far, he is unwilling to do that.
Anybody have any ideas how I could do this? Is there some place in LTM where I could somehow retrieve the last session without relying on a Cookie or some other Header that required the Programmer to send it?
2 Replies
- Kevin_Stewart
Employee
HTTP is stateless, so you need some form of persistence enabled to be able to track multiple requests over multiple TCP connections. If you can't support cookies,
-
Are source IP addresses unique?
-
Is there anything persistent and unique in the Java client's payload?
-
- JP_124708
Nimbostratus
Thanks for the reply. You confirmed that the client needs to provide something that will let me manage the persistence.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com