[SERVER-6227] Definition of serverStatus.network.bytesIn and bytesOut are not consistent with regards to replication traffic Created: 27/Jun/12  Updated: 08/Jan/24  Resolved: 09/Nov/20

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Ryan Nitz Assignee: Amirsaman Memaripour
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-51832 Provide network metrics for egress co... Backlog
Sprint: 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
Participants:
Case:

 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


 Comments   
Comment by Matthew Tretin (Inactive) [ 09/Nov/20 ]

Sorry for the lack of clarity with this ticket closure, benjamingslade@gmail.com.

We did some internal investigation and found that the metrics included in serverStatus.network only include network traffic for ingress connections, when a client or another mongo process initiates communication. In that context, the team has confirmed there are no missing measurements.

But we're going to clarify our documentation through DOCS-13977 and have also opened SERVER-51832 to add metrics that will report on egress connections where the mongo process in question has initiated the connection. I encourage you to watch that ticket for updates.

Comment by Benjamin Slade [ 24/Oct/20 ]

Re: Works as Designed

A bug doesn't have to be in the code, the bug can also be in the design.

Are you saying that having inconsistent definitions for physicalBytesOut and physicalBytesIn is acceptable?

Generated at Thu Feb 08 03:11:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.