[ 
https://issues.apache.org/jira/browse/HDDS-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sreeja updated HDDS-12697:
--------------------------
    Description: 
Create an Ozone debug CLI command to display details of a particular container 
across the datanodes on which it exits.
it should display the following information for the particular container:
 # Container id 
 # Datanode id 
 # State 
 # BCSID
 # Timestamp
 # index value
 # messages if any



Hence should show the complete state transition history for each replica of the 
given container across all datanodes where it exists.

Command should be of the form:
{code:java}
ozone debug log container --db=<path to db> info <container ID>{code}
it also checks for issues (only for the given container) such as:
 * Duplicate OPEN states

 * Mismatched replication

 * Under-replication or over-replication

 * Unhealthy replicas

 * Open-unhealthy replicas

 * Quasi-closed stuck containers

  was:
Create an Ozone debug CLI command to display details of a particular container 
across the datanodes on which it exits.
it should display the following information for the particular container:
 # Container id 
 # Datanode id 
 # State 
 # BCSID
 # Timestamp
 # error message if any
 # Analysis (Duplicate open states , Unhealthy , Mismatched and more)


> Create ozone debug CLI command to display details of a single container
> -----------------------------------------------------------------------
>
>                 Key: HDDS-12697
>                 URL: https://issues.apache.org/jira/browse/HDDS-12697
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Sreeja
>            Assignee: Sreeja
>            Priority: Major
>              Labels: pull-request-available
>
> Create an Ozone debug CLI command to display details of a particular 
> container across the datanodes on which it exits.
> it should display the following information for the particular container:
>  # Container id 
>  # Datanode id 
>  # State 
>  # BCSID
>  # Timestamp
>  # index value
>  # messages if any
> Hence should show the complete state transition history for each replica of 
> the given container across all datanodes where it exists.
> Command should be of the form:
> {code:java}
> ozone debug log container --db=<path to db> info <container ID>{code}
> it also checks for issues (only for the given container) such as:
>  * Duplicate OPEN states
>  * Mismatched replication
>  * Under-replication or over-replication
>  * Unhealthy replicas
>  * Open-unhealthy replicas
>  * Quasi-closed stuck containers



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to