hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12382) Ozone: SCM: BlockManager creates a new container for each allocateBlock call
Date Thu, 31 Aug 2017 20:34:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149557#comment-16149557

Anu Engineer commented on HDFS-12382:

[~nandakumar131] Thanks for the patch. If this blocking your testing in some way, please let
me know I will commit this. Otherwise, I have a patch which changes this code completely but
will take at least a week before it gets patch state. I have some 26 test failures after that

> 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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message