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

Arpit Agarwal updated HDDS-1205:
--------------------------------
          Resolution: Fixed
       Fix Version/s: 0.5.0
    Target Version/s:   (was: 0.5.0)
              Status: Resolved  (was: Patch Available)

I've committed this based on Yetus +1 on the PR.

Let's address the remaining comments in follow up patches before we enable the 
new ReplicationManager by default.

> Refactor ReplicationManager to handle QUASI_CLOSED containers
> -------------------------------------------------------------
>
>                 Key: HDDS-1205
>                 URL: https://issues.apache.org/jira/browse/HDDS-1205
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: SCM
>            Reporter: Nanda kumar
>            Assignee: Nanda kumar
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>         Attachments: HDDS-1205.000.patch, HDDS-1205.001.patch, 
> HDDS-1205.002.patch, HDDS-1205.003.patch
>
>          Time Spent: 7.5h
>  Remaining Estimate: 0h
>
> This Jira is for refactoring the ReplicationManager code to handle all the 
> scenarios that are possible with the introduction of QUASI_CLOSED state of a 
> container.
> The new ReplicationManager will go through the complete set of containers in 
> SCM to find out under/over replicated and unhealthy containers and takes 
> appropriate action.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to