You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Nanda kumar (Jira)" <ji...@apache.org> on 2020/03/02 18:36:00 UTC
[jira] [Updated] (HDDS-3110) Fix race condition in Recon's
container and pipeline handling.
[ https://issues.apache.org/jira/browse/HDDS-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nanda kumar updated HDDS-3110:
------------------------------
Status: Patch Available (was: Open)
> Fix race condition in Recon's container and pipeline handling.
> --------------------------------------------------------------
>
> Key: HDDS-3110
> URL: https://issues.apache.org/jira/browse/HDDS-3110
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Recon
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Major
> Fix For: 0.6.0
>
>
> Fix the following issues in Recon
> * Both the Incremental container report handler and the regular container report handler add new containers from SCM whenever they see a new container. This test and add step must be synchronized between the 2 handlers to avoid any inconsistent metadata state.
> * NodeStateMap in allow does not addition of a single container to the Map of Node -> Set of Containers since it instantiates with a Collections.emptySet(), and then relies on a map.put() to update the value. Changing this to a "new HashSet" allows addition of a container one by one which is possible in Recon.
> * Improve logging in Recon Container Manager when it receives a container report from a node before receiving the pipeline report for a newly created pipeline.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org