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

Enforce the separation between "Router Service" and "Router Role" in the existing server code base

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing

      From a conceptual perspective, "Router Role" and "Router Service" represent two well-separated concepts: a shard node may temporarily assume a "Router Role" to gain the capability of interacting with a "Router Service" (either embedded or external), which is defined by a ServiceEntryPoint, {{CommandRegistry }}

      color: Color value is invalid

      and other pieces of infrastructure.

      Nevertheless, the current state of the server codebase does not clearly reflect this separation: in particular, the "Router Role" expression is often misused or blended with other concerns. As an example, service_entry_point_router_role.cpp contains logic that defines the behavior of the "Router Service Entry Point".

      The objective of this ticket is to audit existing usages of "router role" terminology in the existing code/file names and correct potential inconsistencies.

            Assignee:
            Unassigned Unassigned
            Reporter:
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: