Adding slaveDelay on a passive secondary node stops replication to active secondary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.2
    • Component/s: Replication
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We have a Replica set with
      2 secondary nodes and 1 arbiter.
      One secondary node is set with priority = 0 (passive). We are trying to add a slaveDelay on the passive node.
      After adding delay to passive secondary, using rs.reconfig(). We noticed that the active secondary stops receiving oplogs from primary.
      Once slaveDelay is set, it seems, both active and passive secondary stop receiving oplog/sync.

            Assignee:
            Kristina Chodorow (Inactive)
            Reporter:
            Anup Chatterjee
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: