[
https://issues.apache.org/jira/browse/HDFS-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102729#comment-16102729
]
Anu Engineer commented on HDFS-12178:
-------------------------------------
[~nandakumar131] Would it be possible to check if the error is CONTAINER_EXISTS
and if so just use the container. That way even if 2 calls race each other, we
know that container got created and if not we can retry.
> Ozone: OzoneClient: Handling SCM container creationFlag at client side
> ----------------------------------------------------------------------
>
> Key: HDFS-12178
> URL: https://issues.apache.org/jira/browse/HDFS-12178
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Nandakumar
> Assignee: Nandakumar
> Attachments: HDFS-12178-HDFS-7240.000.patch,
> HDFS-12178-HDFS-7240.001.patch
>
>
> SCM BlockManager provisions a pool of containers upon block creation request,
> only one container is returned with creationFlag to the client. The other
> containers provisioned in the same batch will not have this flag. This jira
> is to handle that scenario at client side, until HDFS-11888 is fixed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
