[jira] [Comment Edited] (HDFS-12299) Race Between update pipeline and DN Re-Registration
[
https://issues.apache.org/jira/browse/HDFS-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420840#comment-16420840
]
Konstantin Shvachko edited comment on HDFS-12299 at 3/30/18 7:05 PM:
-
HDFS-12299.001.branch-2.7.patch broke {{TestRetryCacheWithHA}}. It consistently
fails on branch-2.7 now. Any idea [~jojochuang]?
was (Author: shv):
HDFS-12299.001.branch-2.7.patch broke {{TestRetryCacheWithHA}}. It is
consistently fails on branch-2.7 now. Any idea [~jojochuang]?
> 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.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
[jira] [Comment Edited] (HDFS-12299) Race Between update pipeline and DN Re-Registration
[
https://issues.apache.org/jira/browse/HDFS-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129004#comment-16129004
]
Brahma Reddy Battula edited comment on HDFS-12299 at 8/21/17 10:16 AM:
---
Uploading the test to reproduce this issue.
HDFS-9040 fixes this issue fully in {{trunk}}, So only testcase is added.
HDFS-11817 Partially (null storages were included) fixes in {{branch-2}} and
{{branch-2.8}}. Updated patch to add only {{non-null DatanodeStorageInfo}} at
BlockUnderConstructionFeature#setExpectedLocations
Kindly Review.
was (Author: brahmareddy):
Uploading the test to reproduce this issue.
HDFS-9040 fixes this issue fully in {{trunk}}, So only testcase is added.
HDFS-11817 Partially fixes in {{branch-2}} and {{branch-2.8}}. Updated patch
for full fix(null storages were included).
Kindly Review.
> 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
> Attachments: HDFS-12299-branch-2.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
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDFS-12299) Race Between update pipeline and DN Re-Registration
[
https://issues.apache.org/jira/browse/HDFS-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129004#comment-16129004
]
Brahma Reddy Battula edited comment on HDFS-12299 at 8/21/17 10:14 AM:
---
Uploading the test to reproduce this issue.
HDFS-9040 fixes this issue fully in {{trunk}}, So only testcase is added.
HDFS-11817 Partially fixes in {{branch-2}} and {{branch-2.8}}. Updated patch
for full fix(null storages were included).
Kindly Review.
was (Author: brahmareddy):
Uploading the test to reproduce this issue.
HDFS-9040 fixes this issue fully in {{trunk}}, So only testcase is added.
HDFS-11817 Partially fixes in {{branch-2} and {{branch-2.8}}. Updated patch for
full fix(null storages were included).
Kindly Review.
> 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
> Attachments: HDFS-12299-branch-2.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
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDFS-12299) Race Between update pipeline and DN Re-Registration
[
https://issues.apache.org/jira/browse/HDFS-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129004#comment-16129004
]
Brahma Reddy Battula edited comment on HDFS-12299 at 8/21/17 10:13 AM:
---
Uploading the test to reproduce this issue.
HDFS-9040 fixes this issue fully in {{trunk}}, So only testcase is added.
HDFS-11817 Partially fixes in {{branch-2} and {{branch-2.8}}. Updated patch for
full fix(null storages were included).
Kindly Review.
was (Author: brahmareddy):
Uploading the test to reproduce this issue.
Duplicate of HDFS-11817(HDFS-9040 for trunk). But I feel, this testcase can be
pushed..?
> 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
> Attachments: HDFS-12299-branch-2.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
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
