[ https://issues.apache.org/jira/browse/HDFS-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149589#comment-16149589 ]
Anu Engineer commented on HDFS-12382: ------------------------------------- +1, I will commit this as soon as we have a jenkins run. > Ozone: SCM: BlockManager creates a new container for each allocateBlock call > ---------------------------------------------------------------------------- > > Key: HDFS-12382 > URL: https://issues.apache.org/jira/browse/HDFS-12382 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Reporter: Nandakumar > Assignee: Nandakumar > Attachments: HDFS-12382-HDFS-7240.000.patch > > > {{StorageContainerManager}}'s block protocol creates a new container for each > allocate block call instead of using existing open containers. This behavior > is not seen once the cluster is restarted. > When {{createContainer}} flag is set, the container state is changed from > {{ALLOCATED}} to {{CREATING}}. But in {{refreshContainers}} call only > {{ALLOCATED}} state is handled. > During restart {{loadAllocatedContainers}} loads the {{containers}} map > properly, which fixes the issue after restart. But we will face the same > issue later when we allocate new containers. -- 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