Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Currently, when a container is marked unhealthy by the scanner, there isn't any information persisted as to why this this happened once the datanode logs roll off. In the future we may persist the reason to the container file (if it is still readable), but another option is to have an ozone debug command that can be run on the datanode that will do an on-demand, read-only check of the container and report what it finds.
Attachments
Attachments
Issue Links
- is duplicated by
-
HDDS-2319 CLI command to perform on-demand data scan of a specific container
- Resolved