You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2017/05/26 04:49:04 UTC
[jira] [Created] (HDFS-11888) Ozone: SCM: allocateBlcok does not
set the creationFlag correctly when the open container pool size is greater
than 1
Xiaoyu Yao created HDFS-11888:
---------------------------------
Summary: Ozone: SCM: allocateBlcok does not set the creationFlag correctly when the open container pool size is greater than 1
Key: HDFS-11888
URL: https://issues.apache.org/jira/browse/HDFS-11888
Project: Hadoop HDFS
Issue Type: Sub-task
Components: ozone
Affects Versions: HDFS-7240
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
SCM BlockManager provision a pool of containers upon block creation request that can't be satisfied with current open containers in the pool. However, only one container is returned with the creationFlag to the client. The other container provisioned in the same batch will not have this flag. Client can't assume to use these containers that has not been created on SCM datanodes,
This ticket is opened to fix the issue by persist the createContainerNeeded flag for the provisioned containers. The flag will be eventually cleared by processing container report from datanode when the container report handler is fully implemented on SCM.
For now, we will use a default batch size of 1 for ozone.scm.container.provision_batch_size so that the container will be created on demand upon the first block allocation into the container.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org