[SERVER-48754] Document Server-Internal Ingress Networking Created: 11/Jun/20  Updated: 29/Oct/23  Resolved: 13/Jul/20

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

Type: Task Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Andrew Chen (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Service arch 2020-06-29, Service arch 2020-07-13
Participants:

 Description   

We have a subsystem of specialized code dedicated to networking as a server with clients (ingress). It lives in src/mongo/transport.

Notable classes include (but are not limited to):

  • ServiceExecutor (and derived classes)
  • ServiceStateMachine
  • ReplyBuilderInterface

We should probably also briefly explain traffic capture (TrafficRecorder) that lives in src/mongo/db.

Since ingress networking is mostly invisible to the system at large, we can document it as a single section in src/mongo/transport/README.md.

This is intended to be abstract documentation, describe relationships and state transitions not code in common language.



 Comments   
Comment by Githook User [ 13/Jul/20 ]

Author:

{'name': 'Andrew Chen', 'email': 'a.chen@mongodb.com', 'username': 'AndrooTheChen'}

Message: SERVER-48754 Adding Internal Ingress Networking README
Branch: master
https://github.com/mongodb/mongo/commit/188c858a12705164b7ae5f1ad418821bedd94bb4

Comment by Benjamin Caimano (Inactive) [ 07/Jul/20 ]

FYI, 82fd279 was an artifact of a failed squash. It was followed by an unfortunate squashed revert in 0230f90. The README.md is not yet on master.

Comment by Githook User [ 07/Jul/20 ]

Author:

{'name': 'Andrew Chen', 'email': 'a.chen@mongodb.com', 'username': 'AndrooTheChen'}

Message: SERVER-48754 Adding README to /src/mongo/transport
Branch: master
https://github.com/mongodb/mongo/commit/82fd27960459fd21c57187e0820aa3ceaeaa71c8

Generated at Thu Feb 08 05:17:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.