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
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
Some basic support for group replication was previously added in #1180
However, it is only about understanding single primary groups and being able to display them in the UI, but it does not tackle
anything related to failure detection and recovery.
While group replication has built-in primary election and fail-over, this is only for the group itself. If any group member (be it the primary or any secondary) has traditional async/semi-sync replicas, and it fails, neither group replication nor orchestrator currently fix that.
Hence, this Issue is a feature request so that Orchestrator can fix traditional replicas of group members.
The text was updated successfully, but these errors were encountered:
Some basic support for group replication was previously added in #1180
However, it is only about understanding single primary groups and being able to display them in the UI, but it does not tackle
anything related to failure detection and recovery.
While group replication has built-in primary election and fail-over, this is only for the group itself. If any group member (be it the primary or any secondary) has traditional async/semi-sync replicas, and it fails, neither group replication nor orchestrator currently fix that.
Hence, this Issue is a feature request so that Orchestrator can fix traditional replicas of group members.
The text was updated successfully, but these errors were encountered: