hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-1517) AllocateBlock call fails with ContainerNotFoundException
Date Fri, 17 May 2019 04:59:01 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jitendra Nath Pandey updated HDDS-1517:
---------------------------------------
    Status: Open  (was: Patch Available)

> 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: 0.5h
>  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
(v7.6.3#76005)

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


Mime
View raw message