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

MongoDB WT replication network usage

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.12
    • Component/s: Replication
    • None
    • Environment:
      EC2 Sharded Replicaset
    • Linux

      I have a mongo replica set where all reads/writes must go via the primary. The majority of the writes to the primary are small UPDATES to relatively large documents (~500kB). Each document may have between 5 and 10 updates one after the other.

      Recently I noticed something odd, in that the network IN to the secondaries is MUCH higher than the network IN to the primary. Given that the secondaries should only be handling replication and nothing else I'm at a bit of a loss to explain this effect.

      Here is the network IN over the last hour to the PRIMARY:

      And here is the network IN over the last hour for the two SECONDARIES:

      The network IN on the secondaries appears to average about 200MB (per minute), which is 3 times higher than the 60MB (per minute) of the primary.

      What could explain this?

        1. 1.png
          1.png
          56 kB
        2. 2.png
          2.png
          50 kB
        3. 3.png
          3.png
          52 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            MarcF Marc Fletcher
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: