[
https://issues.apache.org/jira/browse/HDFS-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421053#comment-16421053
]
Konstantin Shvachko commented on HDFS-12299:
--------------------------------------------
Looks like you forgot to backport a part of HDFS-11817, which fixes exactly
this test: {{TestRetryCacheWithHA.testUpdatePipeline()}}. It needs real DN
storageIDs rather than fake ones as before.
Uploaded {noformat}HDFS-12299.002.branch-2.7.patch{noformat}
will revert the old one and recommit the new one.
> Race Between update pipeline and DN Re-Registration
> ---------------------------------------------------
>
> Key: HDFS-12299
> URL: https://issues.apache.org/jira/browse/HDFS-12299
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Priority: Critical
> Fix For: 2.9.0, 3.0.0-beta1, 2.8.2, 2.7.6
>
> Attachments: HDFS-12299-branch-2-002.patch,
> HDFS-12299-branch-2.patch, HDFS-12299.001.branch-2.7.patch,
> HDFS-12299.002.branch-2.7.patch, HDFS-12299.patch
>
>
> *Scenario*
> - Started pipeline with DN1->DN2->DN3
> - DN1 is re-reg and update pipeline is called
> - Update pipeline will success with DN1->DN3->DN4
> - Again update pipeline is called,which will fail with NPE.
> In step3 updatepipeline will set the storages as null since DN1 re-reg(which
> will remove and add the storages)
> {{FSNamesystem#updatePipelineInternal}}
> {code}
> lastBlock.getUnderConstructionFeature().setExpectedLocations(lastBlock,
> storages, lastBlock.getBlockType())
> {code}
--
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
