[
https://issues.apache.org/jira/browse/HDFS-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103065#comment-16103065
]
Nandakumar commented on HDFS-12178:
-----------------------------------
Thanks for the review [~anu].
Introduced additional condition in case of exception to check if it's
CONTAINER_EXISTS error, if not the exception is thrown back to caller.
[~vagarychen], also changed the logic for adding container name to
{{containersCreated}} cache. Now the container is added to the cache only if we
create container successfully or if we get
{{StorageContainerException(CONTAINER_EXISTS)}} exception.
patch v2 uploaded.
> 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, HDFS-12178-HDFS-7240.002.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]
