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

Secondaries of same spec cannot keep up with high primary write load

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Incomplete
    • Affects Version/s: 2.6.7
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL

      Description

      If I put a high continuous write load onto a a replica set I fall behind on the oplog until I fall off the end.

      All three nodes are the same (High) spec - using write concern defaults and a multi threaded insert only workload ( OPLOG, Journal and Collection on same Drive). They are all interconnected by the same network, as is the client.

      I know I could use a higher write concern but this is a simple and likely test scenario and I would expect the replication mechanism to be as fast as any external loader.

        Attachments

          Activity

            People

            Assignee:
            john.page John Page
            Reporter:
            john.page John Page
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: