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

mongos loads config db before listening on its port

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:

      Description

      If the listening port cannot be setup (eg. can't bind because already in use by another mongos, nofile ulimits exceeded, etc), mongos will exit. However, a lot of other state has been setup prior to this, including loading the config db from the config server. In the case where bind() is going to fail, this just adds needless load to the config/shard servers. It would be better if the listening port could first be created and bound to, then the config db loaded and other setup performed, before finally calling accept() on the listening port.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            kevin.pulo Kevin Pulo
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: