Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

If set-identity is used during a restart, the node continues to appear as 'not visible in gossip' in the log #3116

Open
diman-io opened this issue Oct 9, 2024 · 1 comment
Open

If set-identity is used during a restart, the node continues to appear as 'not visible in gossip' in the log #3116

diman-io opened this issue Oct 9, 2024 · 1 comment
Labels
community

Comments

@diman-io
Copy link

diman-io commented Oct 9, 2024

Problem

If set-identity is used during a restart, the node continues to appear as 'not visible in gossip' in the log

Proposed Solution
@diman-io
Copy link
Author

Not sure, maybe I accidentally ran the node on v2, because v1 doesn't allow setting identity while waiting for the cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@diman-io