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.

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

Documentation: proper node takedown #1004

Closed
hds1 opened this issue Jun 15, 2019 · 1 comment
Closed

Documentation: proper node takedown #1004

hds1 opened this issue Jun 15, 2019 · 1 comment
Assignees
Labels
Documentation Issue Missing or incorrect documentation

Comments

@hds1
Copy link

hds1 commented Jun 15, 2019

In the documentation a procedure about a proper node take down is missing.
Maybe an additional note in "Cluster Management Service Configuration Reference" FAQ 1.1.3

"The general way to take down an XRootD data server is to simply kill it. Kill cmsd if node was in a cluster.
The next thing is that the redirector will remember the server for 10 minutes. This is simply because it thinks that maybe it will come back (usually the case but not for you). All this means is that if a client tries to access a file that only existed on the shutdown server the redirector will ask the client to wait until the server comes back up (which it won't). But notice this is a benign action since if that server was the only one that had the file then the only other alternative is to give the client a "not found" error which would terminated the client. So, it only delays enevitable death by 10 minutes."

@abh3 abh3 self-assigned this Jul 3, 2019
@abh3 abh3 added the Documentation Issue Missing or incorrect documentation label Jul 3, 2019
@abh3
Copy link
Member

abh3 commented Apr 11, 2020

The suggestion has been incorporated into the R5 series of documentation (soon on the web).

@abh3 abh3 closed this as completed Apr 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Issue Missing or incorrect documentation
Projects
None yet
Development

No branches or pull requests

2 participants