[
https://issues.apache.org/jira/browse/HDDS-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-5277:
---------------------------------
Labels: pull-request-available (was: )
> Recon shows operational status as "DECOMMISSIONING" for "DECOMMISSIONED" DNs
> ----------------------------------------------------------------------------
>
> Key: HDDS-5277
> URL: https://issues.apache.org/jira/browse/HDDS-5277
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Recon
> Affects Versions: 1.1.0
> Reporter: Nilotpal Nandi
> Assignee: Aravindan Vijayan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.2.0
>
>
> Decommissioned nodes have "DECOMMISSIONING" operational status in recon.
> RCA
> Recon relies on DN heartbeats to understand Node operational state. If the
> node goes down before it reports itself as DECOMMISSIONED, then there is a
> loss of information on Recon side. It is the SCM that moves a node form
> DECOMMISSIONING to DECOMMISSIONED state first, then the Datanode persists the
> state change locally, and then heartbeats with the new state to SCM & Recon
> subsequently. If the DN is shutdown before it can heartbeat the state change
> to Recon, then Recon lives with the stale information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
