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
Normal Scenario - Writes Served by M1, Reads Served by R1
Disaster Master Down - Writes don't work, Reads Served by R1
R1 Promoted to Master (R1 becomes M1) - Writes Served by M1, Reads Fail.
In this Scenario we want Reads to Shift to R2.
First two scenarios are currently handled we need fallback policy for third scenario.
We have replicas which would be in process of updation to master in case of a disaster. Thus first replica may become unavailable while second replica continues to function. In such scenario a Fallback policy would be required.
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently only available policy is random. We need a fallback policy where incase first replica fails we need to fallback to second replica.
Eg.
Source: M1 (master 1)
Replicas: R1 (Replica 1), R2 (Replica 2)
In this Scenario we want Reads to Shift to R2.
First two scenarios are currently handled we need fallback policy for third scenario.
We have replicas which would be in process of updation to master in case of a disaster. Thus first replica may become unavailable while second replica continues to function. In such scenario a Fallback policy would be required.
The text was updated successfully, but these errors were encountered: