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

Improve cluster/mongos health observability

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • None
    • Sharding

    Description

      • We want to improve health observability of sharded clusters so that:
      • We can know, for instance, when a mongos is not capable of taking on more work or having connection issues (whether temporary network or authentication, or other types)
      • We can re-route work appropriately, proactively
      • We can simplify driver logic on retries for mongos

       

      Attachments

        Issue Links

          is depended on by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DRIVERS-1571 Direct read/write retries to another mongos if possible

          • Major - P3 - Major loss of function.
          • Implementing
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-43375 MongoS should differentiate between temporary DNS failures and permanent authentication failures

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              garaudy.etienne@mongodb.com Garaudy Etienne
              Votes:
              2 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: