[
https://issues.apache.org/jira/browse/HDDS-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal resolved HDDS-1559.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.5.0
Target Version/s: (was: 0.5.0)
I've committed this to trunk. Thanks for the contribution [~sdeka].
> 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: [email protected]
For additional commands, e-mail: [email protected]
