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

Definition of serverStatus.network.bytesIn and bytesOut are not consistent with regards to replication traffic

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • None
    • Networking
    • None
    • Service Arch 2019-12-02, Service Arch 2019-12-16, Service Arch 2019-12-30, Service Arch 2020-01-13, Service Arch 2020-01-27, Service Arch 2020-02-10, Service Arch 2020-02-24, Service Arch 2020-03-09, Service Arch 2020-03-23, Service Arch 2020-04-06, Service arch 2020-04-20, Service arch 2020-05-04, Service arch 2020-05-18, Service arch 2020-06-01, Service arch 2020-06-15, Service arch 2020-06-29, Service arch 2020-07-13, Service arch 2020-11-02

    Description

      • serverStatus.network.bytesOut includes network used to serve the oplog to other members of the replica set
      • serverStatus.network.bytesIn does not include network used to consume the oplog from the primary

      Therefore, bytesOut includes replication traffic, but bytesIn does not. We should make this consistent.

      Other things to consider:

      • Make sure that physicalBytesOut/physicalBytesIn have consistent definitions as well
      • What about network used to move chunks?
      • How to account for sharded $lookup
      • How to account for $searchBeta

      Attachments

        Issue Links

          Activity

            People

              amirsaman.memaripour@mongodb.com Amirsaman Memaripour
              rgnitz Ryan Nitz
              Votes:
              3 Vote for this issue
              Watchers:
              30 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: