You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Glen Geng (Jira)" <ji...@apache.org> on 2020/12/16 06:53:00 UTC

[jira] [Created] (HDDS-4599) Properly handle inflight delete/add in ReplicationManager.

Glen Geng created HDDS-4599:
-------------------------------

             Summary: Properly handle inflight delete/add in ReplicationManager.
                 Key: HDDS-4599
                 URL: https://issues.apache.org/jira/browse/HDDS-4599
             Project: Hadoop Distributed Data Store
          Issue Type: Sub-task
          Components: SCM HA
    Affects Versions: 1.1.0
            Reporter: Glen Geng


ReplicationManager maintains the in-flight replication and deletion in-memory, which is not replicated using Ratis. So, theoretically it’s possible that we might run into  data loss issues and over replicated issues if we immediately start ReplicationManager after a failover.

There is a quick fix for the potential data loss issue HDDS-4589, however we need a thorough solution for both in-flight add and in-flight delete.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org