Router port must not accept connections until the shard identity document is set

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2024-03-18, CAR Team 2024-04-01, CAR Team 2024-04-15
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Today, a shard that is not yet added to the cluster is exposing the router port if the embedded router is enabled. If the shard identity document is not yet set, the node may crash if petitions are accepted through the router port, because some shared (shard and router) internal modules are not initialized.

      Goal

      We need to make the router port not accept connections until the shard identity document is set in order to not process petitions when modules are not initialized.

      References

      Estimation

      • User impact: node crashes if user does not follow the correct procedure.
      • Raw Estimation (man day): 3

            Assignee:
            Unassigned
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: