You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/04/24 20:55:07 UTC
[jira] [Commented] (HDFS-12178) Ozone: OzoneClient: Handling SCM
container creationFlag at client side
[ https://issues.apache.org/jira/browse/HDFS-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450930#comment-16450930 ]
Hudson commented on HDFS-12178:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-12178. Ozone: OzoneClient: Handling SCM container creationFlag at (aengineer: rev 72e3016224749c06d8345106fc8165b281bc3c09)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/ozone/web/storage/ChunkGroupOutputStream.java
> 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: Nanda kumar
> Assignee: Nanda kumar
> Priority: Major
> Attachments: HDFS-12178-HDFS-7240.000.patch, HDFS-12178-HDFS-7240.001.patch, HDFS-12178-HDFS-7240.002.patch, HDFS-12178-HDFS-7240.003.patch, HDFS-12178-HDFS-7240.004.patch, HDFS-12178-HDFS-7240.005.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org