[SERVER-7191] Add a method/solution for viewing and/or flushing the cache of all known self-hostnames Created: 27/Sep/12  Updated: 04/Apr/22  Resolved: 04/Apr/22

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 2.0.7, 2.2.0
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Adam Comerford Assignee: Billy Donahue
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

any environment with replication


Issue Links:
Depends
Related
is related to SERVER-14893 Command to flush system hostname cache Backlog
Sprint: Service Arch 2022-04-18
Participants:
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



 Comments   
Comment by Lauren Lewis (Inactive) [ 02/Nov/21 ]

The Service Arch team is in the process of cleaning up tickets in the backlog. This ticket has not been updated in two years so we are closing it. Please reopen if you think this change is valuable.

Generated at Thu Feb 08 03:13:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.