when a connection comes in and matches the rule above, a flow is created to switch all traffic between client and server.
If inside this same flow a new request comes in for a different content rule, the flow needs to be remapped to the new server.
This works fine except when the flow stays idle.
A flow that was idle can't be remapped.
All new requests will be sent to the current/last server even if the request does not match the rule.
The solution is to increase the idle timeout.
You can do this with a 'flow-timeout-multiplier'.
A large value will reduce a lot the chance to see the problem but it also means the amount of resources being used will increase as each flow will remain longer in memory.
It's up to you to find the right balance.
You can do a 'flow stat' from llama mode to see number of free flows and active flows.
I would say you start with a flow-timeout-multiplier of 100 and reduce or increase it if necessary.
Regards,
Gilles.
- please take a moment of your time to rate this answer.
