Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
default behavior should be to remember the nodes we've seen before. we're already storing ip/token pairs in systemtable, but we're not removing them when removetoken is issued.
we probably want to leave some trace of nodes-that-used-to-participate-but-were-removed, but instead of having a historical track in systemtable let's just add something to the gossip listener in StorageService that logs token when a node comes up.
finally, there should be a flag (-D? config?) for bringing up a node in don't-assume-anything-about-the-ring mode as a fallback in case we run into more funky token-related bugs.
Attachments
Attachments
Issue Links
- is related to
-
CASSANDRA-4120 Gossip identifies hosts by UUID
- Resolved
-
CASSANDRA-3485 Gossiper.addSavedEndpoint should never add itself
- Resolved
- relates to
-
CASSANDRA-15823 Support for networking via identity instead of IP
- Triage Needed