[ https://issues.apache.org/jira/browse/HDDS-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674001#comment-16674001 ]
Yiqun Lin commented on HDDS-737: -------------------------------- Haven't fully reviewed for this, looks like the patch is a little large, :). [~nandakumar131], could you give a summary note of the change in your patch? It will be very helpful for others to review. >From a quick glance for the patch.there are lots of deletion logic. Current >change has addressed all the points (*When do we send ICR*) mentioned in >JIRA's description? > Introduce Incremental Container Report > -------------------------------------- > > Key: HDDS-737 > URL: https://issues.apache.org/jira/browse/HDDS-737 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Datanode, SCM > Reporter: Nanda kumar > Assignee: Nanda kumar > Priority: Major > Attachments: HDDS-737.000.patch > > > We will use Incremental Container Report (ICR) to immediately inform SCM when > there is some state change to the container in datanode. This will make sure > that SCM is updated as soon as the state of a container changes and doesn’t > have to wait for full container report. > *When do we send ICR?* > * When a container replica state changes from open/closing to closed > * When a container replica state changes from open/closing to quasi closed > * When a container replica state changes from quasi closed to closed > * When a container replica is deleted in datanode > * When a container replica is copied from another datanode > * When a container replica is discovered to be corrupted -- 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