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

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

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.6.7
    • Component/s: Replication
    • None
    • ALL

      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.

            Assignee:
            john.page@mongodb.com John Page
            Reporter:
            john.page@mongodb.com John Page
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: