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
The properties-driven forest creation currently does not take into account the Host Zone when generating the HA replica forests and assignment.
For customers deployed across multiple data centers, for instance in multiple AWS Availability Zones, it is best to ensure that an HA replica forest is assigned to a host that is in a different Zone. This helps ensure HA if an entire Zone were to be lost. The remaining 2/3 of the cluster would have open replicas and the cluster could remain operational.
This is a common requirement and a best practice that we should look to support and make it easier to achieve.
Several users have asked about how to do this in ml-gradle:
Originally reported at #635
The properties-driven forest creation currently does not take into account the Host Zone when generating the HA replica forests and assignment.
For customers deployed across multiple data centers, for instance in multiple AWS Availability Zones, it is best to ensure that an HA replica forest is assigned to a host that is in a different Zone. This helps ensure HA if an entire Zone were to be lost. The remaining 2/3 of the cluster would have open replicas and the cluster could remain operational.
This is a common requirement and a best practice that we should look to support and make it easier to achieve.
Several users have asked about how to do this in ml-gradle:
The text was updated successfully, but these errors were encountered: