You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/01 02:29:00 UTC

[jira] [Updated] (HDDS-1336) Better block allocation policy in SCM

     [ https://issues.apache.org/jira/browse/HDDS-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arpit Agarwal updated HDDS-1336:
--------------------------------
    Target Version/s: 0.6.0  (was: 0.5.0)

> Better block allocation policy in SCM
> -------------------------------------
>
>                 Key: HDDS-1336
>                 URL: https://issues.apache.org/jira/browse/HDDS-1336
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: SCM
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>
> In case, a client hits close container exception and asks SCM to allocate block for the next write, SCM might allocate blocks from containers which are almost full and can get closed while the client write is still on. Ozone client by default tries 5 times on hitting an exception to write Data to a different block in case it hits CloseContainerException 5 times, it will give up.
> The issue was found while testing with HDDS-1295.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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