Forum Discussion
Fault Tolerance keeping requests in queue.
I have a pool of two members. 1 with priority 1 and other with priority 0. Its kind of fault tolerant. All the requests are entertained by node one. The problem is that the monitors mark the first node down in whatever seconds lets say 7 seconds. In this time all the requests will be drop by node one. I want F5 to keep all requests in between this time in queue and when node 2 comes up it sends all those requests to node 2.
9 Replies
Why F5 experts are not replying to my question? Is it not possible?
- nitass_89166
Noctilucent
In this time all the requests will be drop by node one.
you mean existing connection, don't you? i understand new connection should be sent to the second pool member.
there is reselect option in action on service down but it may not be applicable for your traffic type.
sol15095: Overview of the Action On Service Down feature
https://support.f5.com/kb/en-us/solutions/public/15000/000/sol15095.html- Existing connections would be second option sir, I am talking about the new connections. As second pool member which is passive will come up after specific timeout of active pool member. In between this timeout the new connection will be lost as active member is up but not responding and pool member is passive so not receiving requests.
- nitass
Employee
In this time all the requests will be drop by node one.
you mean existing connection, don't you? i understand new connection should be sent to the second pool member.
there is reselect option in action on service down but it may not be applicable for your traffic type.
sol15095: Overview of the Action On Service Down feature
https://support.f5.com/kb/en-us/solutions/public/15000/000/sol15095.html- Existing connections would be second option sir, I am talking about the new connections. As second pool member which is passive will come up after specific timeout of active pool member. In between this timeout the new connection will be lost as active member is up but not responding and pool member is passive so not receiving requests.
- nitass
Employee
As second pool member which is passive will come up after specific timeout of active pool member. In between this timeout the new connection will be lost as active member is up but not responding and pool member is passive so not receiving requests.
i am not aware of the queuing functionality you are talking about. could it be okay if bigip responds with something until the second pool member is up and ready such as holding page?
- I have a VS with no http profile attached. 1 pool and 2 pool members A and B. A has priority 1 and becomes active member and B has priority 0 and becomes passive member. All the traffic goes to member A. ICMP help monitor is configured with interval 2 seconds and timeout 7 seconds. For example now the member A stopped responding But F5 will mark member A down after 7 seconds and after that passive member B will come up and start responding to traffic. But in between these 7 seconds all the new requests will lost as VS was sending traffic to A which was not responding and B was in passive state and VS was not sending traffic to B. What i want is that F5 keep new connections in queue for 7 seconds and send it to member B when VS mark member A down and start sending traffic to member B.
- nitass_89166
Noctilucent
As second pool member which is passive will come up after specific timeout of active pool member. In between this timeout the new connection will be lost as active member is up but not responding and pool member is passive so not receiving requests.
i am not aware of the queuing functionality you are talking about. could it be okay if bigip responds with something until the second pool member is up and ready such as holding page?
- I have a VS with no http profile attached. 1 pool and 2 pool members A and B. A has priority 1 and becomes active member and B has priority 0 and becomes passive member. All the traffic goes to member A. ICMP help monitor is configured with interval 2 seconds and timeout 7 seconds. For example now the member A stopped responding But F5 will mark member A down after 7 seconds and after that passive member B will come up and start responding to traffic. But in between these 7 seconds all the new requests will lost as VS was sending traffic to A which was not responding and B was in passive state and VS was not sending traffic to B. What i want is that F5 keep new connections in queue for 7 seconds and send it to member B when VS mark member A down and start sending traffic to member B.
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