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

Nanda kumar updated HDDS-1336:
------------------------------
    Target Version/s: 0.7.0  (was: 0.6.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
>              Labels: Triaged
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to