[
https://issues.apache.org/jira/browse/HDDS-1559?focusedWorklogId=246251&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-246251
]
ASF GitHub Bot logged work on HDDS-1559:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/May/19 17:46
Start Date: 21/May/19 17:46
Worklog Time Spent: 10m
Work Description: supratimdeka commented on pull request #841: HDDS-1559.
Include committedBytes to determine Out of Space in VolumeChoosingPolicy.
Contributed by Supratim Deka
URL: https://github.com/apache/hadoop/pull/841
https://issues.apache.org/jira/browse/HDDS-1559
This patch improves the space availability check in chooseVolume by
inclusion of committed space(committedBytes in HddsVolume) in the equation.
Container create fails with Exception if there isn't sufficient available space.
The handling/management of the exception in Ratis is not modified in this
patch. That will be scoped separately as part of Datanode IO Failure handling
work.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 246251)
Time Spent: 10m
Remaining Estimate: 0h
> 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: 10m
> 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: [email protected]
For additional commands, e-mail: [email protected]
