custom load balancing

Thanks for the response!

 

 

I thought about the status check page, one exists already, our dev folks would just need to add that parameter to the check list. My only concern was that marking it down would prevent existing persistent conns to be redirect to another host.

 

 

On the other idea, yea I thought of an iRule as well. Our devs could add a header/URI value that could be parsed on server response, but I wasn't sure what you could actually do with that with respect to LB preference. I know you could persist on that value, but what I would need is to collect those values and set some sort of precedence to the pool member.

 

 

I guess what I need is some sort of living member preference list, say a server has 10 out of a 100 available work loads, it would have a higher precedence than the server with 50 or 90.

 

 

I am thinking your option one might be my only bet. Which would just prevent the LB from sending additional work to a already fully loaded server.

 

 

peter