Skip to content

Primary/Secondary server Internals with OpLog  #27

Open
@anupkumarsharma

Description

@anupkumarsharma

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions