Rack aware whitelisting or rackaware load balancing policy

Description

With the way applications are now used, where appA is in availability zone A with rackA, there should be a rack aware load balancing policy or some way to prefer rackA nodes over rackB nodes. In this case, we’d like to use appA with rackA and appB with rackB, but we also would like failover capability in case rackA stops responding. I know it’s an unlikely scenario where appA is working, but several nodes in rackA are down, but it’s still a possibility, thus the request for failover capability.

We are using something like this:

In this case, it might work if we could do the above, but weight the nodes instead of ignoring. Like:

rackA (node 1,2,3) weight = 1

rackB (node 4,5,6) weight = .75

rackC (node 7,8,9) weight = .25

Thus, we’d prefer anything with a higher weight, unless it was unavailable.

Environment

None

Pull Requests

None

Activity

Show:

Ammar Khaku March 26, 2024 at 9:13 PM

I believe will tackle this use case.

Details

Assignee

Reporter

Labels

Affects versions

Priority

Created August 18, 2022 at 9:01 PM
Updated March 26, 2024 at 9:13 PM