[
https://issues.apache.org/jira/browse/HDDS-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose resolved HDDS-1336.
------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
HDDS-8329 added a wait in the SCM between allocating the last block to a
container and sending the close command to the datanode to give the last writes
to the container a chance to complete. This looks to be the same issue so I am
resolving it as fixed.
> Better block allocation policy in SCM
> -------------------------------------
>
> Key: HDDS-1336
> URL: https://issues.apache.org/jira/browse/HDDS-1336
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Labels: Triaged
> Fix For: 1.4.0
>
>
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
