[
https://issues.apache.org/jira/browse/HDFS-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450967#comment-16450967
]
Hudson commented on HDFS-12382:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-12382. Ozone: SCM: BlockManager creates a new container for each
(aengineer: rev 3c8f1c53b2feba92f486bf6f542b36209ce12e3b)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/ozone/scm/block/BlockManagerImpl.java
> 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: Nanda kumar
> Assignee: Nanda kumar
> Priority: Major
> Fix For: HDFS-7240
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
