[
https://issues.apache.org/jira/browse/HDDS-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3361:
---------------------------------
Labels: pull-request-available (was: )
> Change replication logic to use PersistedOpState
> ------------------------------------------------
>
> Key: HDDS-3361
> URL: https://issues.apache.org/jira/browse/HDDS-3361
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: SCM
> Affects Versions: 0.6.0
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
>
> In an earlier change, we decided that the Datanode would change the state of
> decommissioning / maintenance replicas and report the new state in its
> container report. Using that assumption, the logic in replication manager was
> changed to expect the ContainerReplica to contain the decom / maintenance
> state.
> However in HDDS-2592 it was decided that the DN would simply store the
> operational state and report only the operation state in the heartbeat. This
> state is reported back to SCM and stored in the datanodeDetails instances.
> This means that earlier assumption (ContainerReplica will contain the decom
> state) is no longer valid.
> This Jira is to change the logic so replication decisions are based on the
> "persistedOpState" in the datanode details object instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
