-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
add node manager to make nodes peer-stoppable #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider adding a doc for how to use this?
#### Experimental feature: Peer-stopping | ||
|
||
An experimental feature is peer-stopping. A node can not only stop itself but also other nodes. To do this, send | ||
a message to the channel `f"shutdown:{self.node_name}"` and the node manager will shutdown all of the nodes in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this sentence does not seem to make sense, a specific name and all?
f"shutdown:{self.node_name}"
and the node manager will shutdown all of the nodes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, the channel name is meant to indicate where the shutdown signal comes from. And right now, I only implemented shutdown all nodes function. Do you think this is enough for your use case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that should work, it's just the sentence is a little bit ambigous
No description provided.