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
I had searched in the issues and found no similar issues.
Motivation
As mentioned in #1219 (comment), the master can check if the cluster topology is matched by the host and port when receiving the replicate request. It can reduce the risk of the replica connecting to the stale master.
BTW, we can also have a mechanism(configuration) to let users disable this feature.
Solution
For the replication check, check if the replica's IP and port are in the master replica nodes. And add a configuration to allow users to enable and disable it in flight.
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Motivation
As mentioned in #1219 (comment), the master can check if the cluster topology is matched by the host and port when receiving the replicate request. It can reduce the risk of the replica connecting to the stale master.
BTW, we can also have a mechanism(configuration) to let users disable this feature.
Solution
For the replication check, check if the replica's IP and port are in the master replica nodes. And add a configuration to allow users to enable and disable it in flight.
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: