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

Add a method/solution for viewing and/or flushing the cache of all known self-hostnames

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Do
    • Affects Version/s: 2.0.7, 2.2.0
    • Fix Version/s: None
    • Component/s: Networking
    • Labels:
      None
    • Environment:
      any environment with replication
    • Case:

      Description

      This stems from the fact that "can't find self in new replset config" is triggered if a member doesn't find exactly one "self" in the config.

      As such, if there are multiple entries it can cause problems, and each mongod process that is a member of a replica set caches all known self-hostnames they've learned about since the process started.

      Therefore a solution is needed to determine what the contents of this cache is (or to clear it) so that issues that trigger "can't find self" can be predicted and circumvented

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-servicearch Backlog - Service Architecture
              Reporter:
              adam@comerford.net Adam Comerford
              Participants:
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: