Pool membership kills connections

Hello all,

 

 

I've been trying to figure out a good way to solve a problem.

 

 

We have a pool of six web application nodes, monitored via a call to a "health" page on each node (GET /health).

 

 

If the health page does either not respond, or responds with a status code not specified in the response string, then the node is marked down from the pool.

 

 

As traffic increases, the health page will become unavailable due to load on the web server.

 

 

It seems that when a node is marked down, no more traffic will be sent to that node, effectively killing off any user sessions established on that node.

 

 

Is there a way to makes the node remain in the pool for existing connections/sessions, and simply not send new (sessions without a cookie) connections to this node?

 

 

It seems like there should be a way to do this, and I must be overlooking something simple.

 

 

Any help is appreciated!