Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-10474

How does replication work and what is the performance bottlenecks?

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: 2.2.3
    • Fix Version/s: None
    • Component/s: Replication
    • Environment:
      Ubuntu LTS

      Description

      We've been having issues with replication lag.
      Had to manually restart one of two slaves and use db.adminCommand(

      {replSetMaintenance:true}

      ), let it sync up and then do the same for the other slave. Only then were both able to catch up with the oplog.

      Why does it help to restart mongodb for it to start catching up when 1800+ seconds behind? Did not help to set maintenance mode.

      What's the bottlenecks of replication?
      Does all "repl writer workers" have to wait for the one writer thread to get the oplog replication done?
      Did not seem to utilize much of the resources available when the replication was stalled.

      Will the maximum capacity to replicate one database depend on how much one cpu core can handle? How do we monitor this limitation?

        Attachments

          Activity

            People

            Assignee:
            stennie Stennie Steneker
            Reporter:
            balboah Johnny Boy
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: