[jira] [Commented] (HDDS-1559) Include committedBytes to determine Out of Space in VolumeChoosingPolicy
[ https://issues.apache.org/jira/browse/HDDS-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850517#comment-16850517 ] Hudson commented on HDDS-1559: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16620 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16620/]) HDDS-1559. Include committedBytes to determine Out of Space in (arp7: rev 346c2b798080cc1f22d6ba85e584141e7dee2c08) * (edit) hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/ozoneimpl/TestOzoneContainer.java * (edit) hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/volume/RoundRobinVolumeChoosingPolicy.java > Include committedBytes to determine Out of Space in VolumeChoosingPolicy > > > Key: HDDS-1559 > URL: https://issues.apache.org/jira/browse/HDDS-1559 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Datanode >Reporter: Supratim Deka >Assignee: Supratim Deka >Priority: Major > Labels: pull-request-available > Fix For: 0.5.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > This is a follow-up from HDDS-1511 and HDDS-1535 > Currently when creating a new Container, the DN invokes > RoundRobinVolumeChoosingPolicy:chooseVolume(). This routine checks for > (volume available space > container max size). If no eligible volume is > found, the policy throws a DiskOutOfSpaceException. This is the current > behaviour. > However, the computation of available space does not take into consideration > the space > that is going to be consumed by writes to existing containers which are still > Open and accepting chunk writes. > This Jira proposes to enhance the space availability check in chooseVolume by > inclusion of committed space(committedBytes in HddsVolume) in the equation. > The handling/management of the exception in Ratis will not be modified in > this Jira. That will be scoped separately as part of Datanode IO Failure > handling work. -- 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
[jira] [Commented] (HDDS-1559) Include committedBytes to determine Out of Space in VolumeChoosingPolicy
[ https://issues.apache.org/jira/browse/HDDS-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849277#comment-16849277 ] Hudson commented on HDDS-1559: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16611 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16611/]) HDDS-1559. Fix TestReplicationManager. Contributed by Bharat (xyao: rev b70d1be685c5f9d08ab39f9ea73fc0561e037c74) * (edit) hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/container/TestReplicationManager.java > Include committedBytes to determine Out of Space in VolumeChoosingPolicy > > > Key: HDDS-1559 > URL: https://issues.apache.org/jira/browse/HDDS-1559 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Datanode >Reporter: Supratim Deka >Assignee: Supratim Deka >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > This is a follow-up from HDDS-1511 and HDDS-1535 > Currently when creating a new Container, the DN invokes > RoundRobinVolumeChoosingPolicy:chooseVolume(). This routine checks for > (volume available space > container max size). If no eligible volume is > found, the policy throws a DiskOutOfSpaceException. This is the current > behaviour. > However, the computation of available space does not take into consideration > the space > that is going to be consumed by writes to existing containers which are still > Open and accepting chunk writes. > This Jira proposes to enhance the space availability check in chooseVolume by > inclusion of committed space(committedBytes in HddsVolume) in the equation. > The handling/management of the exception in Ratis will not be modified in > this Jira. That will be scoped separately as part of Datanode IO Failure > handling work. -- 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
