Skip to content

Conversation

@ProKil
Copy link
Owner

@ProKil ProKil commented Dec 2, 2024

No description provided.

Copy link
Collaborator

@XuhuiZhou XuhuiZhou left a 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
Copy link
Collaborator

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

Copy link
Owner Author

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?

Copy link
Collaborator

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

@ProKil ProKil merged commit b7b3347 into main Jan 18, 2025
4 checks passed
@ProKil ProKil deleted the feature/node-manager branch January 18, 2025 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants