Recovery status reported for any status other than COMPLETE #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
According lprocfs_recovery_status_seq_show() in Lustre 2.13, valid "status" values in recovery_status are: COMPLETE The target is active and handling requests WAITING The target is active but waiting for another MDT WAITING_FOR_CLIENTS The target is active but no clients have connected RECOVERY The target is active and recovering after failover INACTIVE The target is inactive For individual targets, for all states other than COMPLETE, display the recov_status field instead of metric values. This makes it easier for the admin to see unhealthy targets. At the top of the window, report the lowest-numbered MDT which is not COMPLETE or INACTIVE. If an MDT is INACTIVE, it was set that way by an admin and she likely already knows - but other states may not be expected and should be brought to her attention. Signed-off-by: Olaf Faaland <[email protected]>
|
@morrone or @tonyhutter , can you take a look? Thanks! |
|
Cherry-picked to master at 7c7266e |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In a multi-MDT system, under Lustre 2.10, all MDTs connect to each other via exports/imports. If one MDT cannot connect to one or more other MDTs, it will not service requests and will refuse connections from clients. There are other target states which may indicate action is required by an admin. These states are reflected in the "recovery_status" procfile exported by Lustre targets.
However, for LMT 3.2.7 and some releases before that, MDTs in such a state were not reported as such in ltop, because ltop checked for "RECOV" in the status field, indicting recovery, but did not check for the strings corresponding to any other states.
According lprocfs_recovery_status_seq_show() in Lustre 2.13,
valid "status" values in recovery_status are (roughly):
For individual targets, for all states other than COMPLETE, display the
recov_status field instead of metric values. This makes it easier for
the admin to see unhealthy targets.
At the top of the window, report the lowest-numbered MDT which is not
COMPLETE or INACTIVE. If an MDT is INACTIVE, it was set that way by
an admin and she likely already knows - but other states may not be
expected and should be brought to her attention.