one of our service has problem:
on server site, there is warning messages same as below:
Warning: The session id: sessionID has been accessed from currentServer, a server that is neither the primary (primaryServer) nor the secondary (secondaryServer). The request URL was: requestUrl
The session id: sessionID has been accessed from currentServer, a server that is neither the primary (primaryServer) nor the secondary (secondaryServer). Repeated occurrences of this can cause memory problems and performance degredation, as sessions are loaded into memory on more than two servers at a time.
The most likely cause is a configuration error on a front end hardware loadbalancer or webserver plugin. They should be configured to respect the values of primary/secondary in the cookie (i.e., stickyness), when possible.
Please ensure that the front end webserver or load-balancer has been properly configured.
I have been adviced that I need increase idle timeout.
but, I still do not understand this problem should increase idle timeout or stickness timeout?
if it is idle timeout, the server is 3 min, but, I looked CSS default, it only 8 second, so, do I cause any problem if I increase to 3 min?
If it is stickness inact timeout, server site has not document about it, how many I should set?
my configuration is:
vip address 10.1.1.10
add service myservice-myhost1-80
add service myservice-myhost2-80
ip address 10.2.2.11
keepalive type http
keepalive uri "/webct/checkStatusForLb"
keepalive frequency 30
Any comments will be apprecaited
Thanks in advance
you can increase the ilde timeout as much as you want.
The only thing you need to keep an eye on is the number of flows active on the box.
This number is limited.
So by increasing idle timeout you make flow stay longer in memory.
So, the command to use is a 'flow stats'
Check for free FCB.
use the command 'flow-timeout-multiplier 15' to bump the connection idle timeout to 15 x 16 = 240 sec ( 4min).
This is what is needed in your case.