hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1517) AllocateBlock call fails with ContainerNotFoundException
Date Tue, 21 May 2019 16:31:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1517?focusedWorklogId=246179&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-246179

ASF GitHub Bot logged work on HDDS-1517:

                Author: ASF GitHub Bot
            Created on: 21/May/19 16:30
            Start Date: 21/May/19 16:30
    Worklog Time Spent: 10m 
      Work Description: bshashikant commented on pull request #826: HDDS-1517. AllocateBlock
call fails with ContainerNotFoundException.
URL: https://github.com/apache/hadoop/pull/826#discussion_r286116624

 File path: hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/container/ContainerStateManager.java
 @@ -296,10 +296,10 @@ ContainerInfo allocateContainer(
-    pipelineManager.addContainerToPipeline(pipeline.getId(),
 Review comment:
   Addressed in the latest patch.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 246179)
    Time Spent: 1h 20m  (was: 1h 10m)

> AllocateBlock call fails with ContainerNotFoundException
> --------------------------------------------------------
>                 Key: HDDS-1517
>                 URL: https://issues.apache.org/jira/browse/HDDS-1517
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: SCM
>    Affects Versions: 0.5.0
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.4.1
>         Attachments: HDDS-1517.000.patch
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> In allocateContainer call,  the container is first added to pipelineStateMap and then
added to container cache. If two allocate blocks execute concurrently, it might happen that
one find the container to exist in the pipelineStateMap but the container is yet to be updated
in the container cache, hence failing with CONTAINER_NOT_FOUND exception.

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