[HDDS-1559] Include committedBytes to determine Out of Space in VolumeChoosingPolicy

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Component/s: Ozone Datanode
• Labels: pull-request-available
• Sprint: Done
• Assignee: Supratim Deka
• Reporter: Supratim Deka
• Created: 20/May/19 03:30
• Updated: 24/Feb/20 20:51
• Resolved: 29/May/19 03:48

Description

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.

Issue Links

• links to: GitHub Pull Request #841