Prioritize webapp access

I have two load-balanced red-hat 7.3 servers, prod1 and prod2. For a particular resin webapp, http://website/webapp, I would like to have my traffic go only to prod1. If prod1 is down, I would like to point the traffic for that webapp to prod2. For the rest of my traffic, I would like to keep it load-balanced between prod1 and prod2. I've been told that my RedHill WebMux load balancer does not have the capability of splitting the traffic this way. I also have a red-hat/ resin staging server which could be used to determine traffic routes. Please let me know if you have any workaround suggestions.

Thanks,
El Debarge
EldebargeAsked:
Who is Participating?
 
ahoffmannConnect With a Mentor Commented:
I'd use a iptables DNAT rule to route port 80, 443, whatelse to prod1, then tell your watchdog (probably part of your loadbalance software) to remove this rule and set it up for prod2 if prod1 is down
0
 
jlevieCommented:
Sounds to me like you just need a more capable load balancer, perhaps something like a Cisco Local Director. If I read the doc's right you can do content prioritzation which allows a specific URL(s) to be directed at a particular server with failover.
0
 
EldebargeAuthor Commented:
Thank you for the load balancer upgrade suggestion. Before I commit to the hardware upgrade costs, I'd like to make sure that there aren't any OS/programming alternatives.

Thanks
El Debarge
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
jlevieCommented:
I can't think of any software solutions that you could use. The load balancer has to know what to do with the traffic and that happens before the requests get to the Linux boxes. Before buying anything I'd want an assurance from a Cisco Engineer or a re-seller (in writing) that the Local Director can be configured for this particular mix of load balancing.
0
 
ahoffmannCommented:
> If prod1 is down, I would like to point the traffic for that webapp to prod2.
> For the rest of my traffic, I would like to keep it load-balanced between prod1 and prod2.

hmm, how should traffic be balanced between prod1 and prod2 if prod1 is down?
Well, the rule for that case is simple: all traffic to prod2. Dot.
Couls you please explain what your description means.
0
 
EldebargeAuthor Commented:
From the onset, "all other traffic" should be load-balanced from prod1 and prod2. Yes, if prod1 is down then all traffic will have to go to prod2. But this rule should be different than the traffic for the particular webapp, which will only use prod1 until prod1 is unavailable.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.