Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Primary/Secondary server Internals with OpLog #27

Open
anupkumarsharma opened this issue May 31, 2018 · 0 comments
Open

Primary/Secondary server Internals with OpLog #27

anupkumarsharma opened this issue May 31, 2018 · 0 comments

Comments

@anupkumarsharma
Copy link

Hey, This is more of a question than an issue.
I was looking into another connector Debezium and found a special case where they search for a primary server in the replication set. This solution doesn't handle this case. So, how does it affect when we have multiple replication sets and there is primary server failure?

Please correct me if I am wrong, but when the primary server handles an operation, it generates an oplog. This log then gets synced to other secondary servers. In our case since we maintain offset, even let say we lost connection to the primary. In this case, if we now switch to secondary server oplog, all the process will do is wait for the offset, until the secondary server's oplog get synced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant