You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now RestClient accepts a set of hosts it will rotate through doing client-side load balancing. When the server runs in AWS it's good practice to spread instances across multiple availability zones and to make requests within your availability zone preferably, falling back to out of zone requests when necessary. It would be good to have two sets of addresses RestClient rotates through. One is the primary set which can be filled with client/data nodes within your availability zone and the other one is secondary set where client/data nodes outside of your availability zone will reside. In this case, a client should rotate primary nodes (even if there's only one node) and fallback to secondary nodes when the primary is empty/blacklisted.
The text was updated successfully, but these errors were encountered:
Right now RestClient accepts a set of hosts it will rotate through doing client-side load balancing. When the server runs in AWS it's good practice to spread instances across multiple availability zones and to make requests within your availability zone preferably, falling back to out of zone requests when necessary. It would be good to have two sets of addresses RestClient rotates through. One is the primary set which can be filled with client/data nodes within your availability zone and the other one is secondary set where client/data nodes outside of your availability zone will reside. In this case, a client should rotate primary nodes (even if there's only one node) and fallback to secondary nodes when the primary is empty/blacklisted.
The text was updated successfully, but these errors were encountered: