[
https://issues.apache.org/jira/browse/HDDS-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845825#comment-16845825
]
Hudson commented on HDDS-1517:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16586 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16586/])
HDDS-1517. AllocateBlock call fails with ContainerNotFoundException
(shashikant: rev a315913c48f475a31065de48a441c7faae89ab15)
* (edit)
hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/container/TestSCMContainerManager.java
* (edit)
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/container/SCMContainerManager.java
* (edit)
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/container/ContainerStateManager.java
* (edit)
hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/block/TestBlockManager.java
> 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 40m
> 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: [email protected]
For additional commands, e-mail: [email protected]
