-
Notifications
You must be signed in to change notification settings - Fork 638
Release node name on graceful shutdown #9734
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
Comments
@CyberROFL , @pixcc, it seems like the name release should be done here correct ? If so, is it as easy as setting the node's name attribute to |
In fact, there's already a pull-request here, with almost all the necessary changes. But its author hasn't made any updates for quite a long time. I'll try to ask him if he's still interested in it.
Almost, this is the process of releasing the name if the node is re-registered as serving different database. In this context subdomain, tenant and database are synonyms. The node name is formed from the prefix You can read more about this feature in docs.
It's actually a little more complicated than just setting the name attribute to
It is defined here. |
I reached the author of the pull request. He said he's interested in finishing this pull-request, there's really not much left, he's almost done. But there are many other issues that are suitable for newcomers as well. I can help you find a task that interests you in the field of the Node Broker or database backups. |
Hey @pixcc, thank you so much for the information you've provided, I've got some reading to do ! Thanks for sharing the PR already made for this. It's nice to have it so that can (try to) understand it. Regarding the other issues to work on, how about this one ? Otherwise feel free to mention me and/or assign me on one you feel that fits best. Thanks |
Node should release its custom name (if used) on graceful shutdown, allowing it to be used immediately for another node.
The text was updated successfully, but these errors were encountered: