[
https://issues.apache.org/jira/browse/HDFS-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155987#comment-16155987
]
Anu Engineer commented on HDFS-12252:
-------------------------------------
HDFS-12387 does address this. We might be able to resolve this JIRA once that
is committed.
> Ozone: SCM: Container State Machine -1- Track container creation state in SCM
> -----------------------------------------------------------------------------
>
> Key: HDFS-12252
> URL: https://issues.apache.org/jira/browse/HDFS-12252
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Labels: ozoneMerge
>
> Currently, SCM only persist the pipeline info of a container in container.db
> upon allocation. This provides better scalability which offloads the query of
> container info to datanodes.
> However, this is not enough enough information for SCM to provide shared
> container service as other clients may not know the container creation state
> on datanodes by the creator of the container.
> This is the first patch that introduces container states on SCM and ACK
> message from creator of the container to update/persist the container state
> on SCM container store.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
