CirrostratusGood day all,
In forcing a pool member down (pool has two members), what will result for existing user sessions to the member which will/is being made down.
how is the expected behaviour from big-ip.
Thanks in advance.
NacreousHi
This info can be found here - https://support.f5.com/csp/article/K13310
Pertinent points being...
When set to Disabled, a node or pool member continues to process persistent and active connections. It can accept new connections only if the connections belong to an existing persistence session.
When set to Forced Offline, a node or pool member allows existing connections to time out, but no new connections are allowed.
CirrostratusWhat is the case when one of the member is not taken down by big-ip administrator, but one of the the actual member server is either shut down or is restarting? How will existing traffic to that member behave?
NacreousThat depends on what you have set the Action on Service Down setting to be - see https://support.f5.com/csp/article/K15095
Default behaviour would be to reload balance connections to a different pool member, this would include persistent connection
CirrostratusIf by default it rebalance connections to other available member, will the users connection to previous member (which now has gone down) disrupt momentarily before moving to another available member. how will the user experience be in this case?
Thanks.
NacreousIt really depends on the protocol. If this is HTTP then I would expect the client to retry the request. Other protocols will behave differently