[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 274
  • Last Modified:

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
0
Eldebarge
Asked:
Eldebarge
  • 2
  • 2
  • 2
1 Solution
 
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
 
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
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
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
 
ahoffmannCommented:
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

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now