Forcing the use of a new pool and new member based on the current pool and member

It might get a bit more complicated than that:

 

 

- Can a client ever make a request directly to Pool-A first? If so, do you want to also map the pool members the other way to Pool-B?

 

 

- What do you want to happen if one pool member from Pool-A is down but the corresponding pool member from Pool-B is up?

 

 

I think it might be cleaner to use persistence to enforce this logic. When a request is made to either pool, you could insert a persistence cookie for both pools that maps member one from Pool-A to member one in Pool-B.

 

 

You could also configure monitors that would mark both corresponding pool members down if either paired pool member was down.

 

 

Aaron