Forum Discussion
Universal Persistence Issue
We have an custom iRule in which we are doing universal persistence on the value present in the http header.
The iRule is :
when HTTP_REQUEST {
}
As per the theory persistence record should be maintained based upon the value of orgId in the http header with timeout of 300 seconds.
But we are seeing that some of the requests about ~25% are not getting sticked to one node and they are gettting load balanced to other nodes.
Is there any thing which we are doing wrong here? Our intention is to have orgId value persistence record should be sticked to only node in the above pools (chan and prsn).
Can anybody help?
Thanks.
Narendra
- hooleylistCirrostratusHi Narenda,
when HTTP_REQUEST { switch -glob [string tolower [HTTP::uri]] { "/api/channel*" { pool "umps-gus1-chan-pool" persist uie [HTTP::header "orgId"] 300 log local0. "[IP::client_addr]:[TCP::client_port]: Using umps-gus1-chan-pool" } "/api/presence*" { pool "umps-gus1-prsn-pool" persist uie [HTTP::header "orgId"] 300 log local0. "[IP::client_addr]:[TCP::client_port]: Using umps-gus1-prsn-pool" } default { pool "umps-gus1-nginx-pool" log local0. "[IP::client_addr]:[TCP::client_port]: Using umps-gus1-nginx-pool" persist none } } } when LB_SELECTED { log local0. "[IP::client_addr]:[TCP::client_port]: Selected [LB::server]" } when SERVER_CONNECTED { log local0. "[IP::client_addr]:[TCP::client_port]: Connected: [IP::server_addr]:[TCP::server_port], [LB::server]" }
- Narendra_26827NimbostratusThanks hoolio. Will try to do that.
- nitassEmployeeIt is suspected the request is getting load balanced from external bigips to the internal bigips due to this separate persistence record is getting created for the same orgId. i do not think so. external bigip uses source address persistence, so all request from one client should be forwarded to same internal bigip.
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