hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1559) Include committedBytes to determine Out of Space in VolumeChoosingPolicy
Date Fri, 24 May 2019 06:28:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1559?focusedWorklogId=247909&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-247909

ASF GitHub Bot logged work on HDDS-1559:

                Author: ASF GitHub Bot
            Created on: 24/May/19 06:27
            Start Date: 24/May/19 06:27
    Worklog Time Spent: 10m 
      Work Description: supratimdeka commented on issue #841: HDDS-1559. Include committedBytes
to determine Out of Space in VolumeChoosingPolicy. Contributed by Supratim Deka
URL: https://github.com/apache/hadoop/pull/841#issuecomment-495488583
   the checkstyle errors reported here are not a part of this patch. these were introduced
in SCMContainerPlacementRackAware.java by HDDS-700 and got submitted into trunk yesterday.
   I think we can ignore these checkstyle errors reported for this patch because they already
exist on the main branch. Right?
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:

Issue Time Tracking

    Worklog Id:     (was: 247909)
    Time Spent: 1h  (was: 50m)

> 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
>  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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message