Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 26 May 2017 15:37:05 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13073405.1495196005000.303356.1495813025232@Atlassian.JIRA>
In-Reply-To: <JIRA.13073405.1495196005000@Atlassian.JIRA>
References: <JIRA.13073405.1495196005000@Atlassian.JIRA> <JIRA.13073405.1495196005003@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HDFS-11856) Ability to re-add Upgrading Nodes
 (remote) to pipeline for future pipeline updates
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 26 May 2017 15:37:11 -0000


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

Kihwal Lee updated HDFS-11856:
------------------------------
    Attachment: HDFS-11856-02.branch-2.patch

Reattaching the branch-2 patch with a different name to kick the pre-commit.

> Ability to re-add Upgrading Nodes (remote) to pipeline for future pipeline updates
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-11856
>                 URL: https://issues.apache.org/jira/browse/HDFS-11856
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client, rolling upgrades
>    Affects Versions: 2.7.3
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-11856-01.patch, HDFS-11856-02.branch-2.patch, HDFS-11856-02.patch, HDFS-11856-branch-2-02.patch, HDFS-11856-branch-2.7-02.patch, HDFS-11856-branch-2.8-02.patch
>
>
> During rolling upgrade if the DN gets restarted, then it will send special OOB_RESTART status to all streams opened for write.
> 1. Local clients will wait for 30 seconds to datanode to come back.
> 2. Remote clients will consider these nodes as bad nodes and continue with pipeline recoveries and write. These restarted nodes will be considered as bad, and will be excluded for lifetime of stream.
> In case of small cluster, where total nodes itself is 3, each time a remote node restarts for upgrade, it will be excluded.
> So a stream writing to 3 nodes initial, will end-up writing to only one node at the end, there are no other nodes to replace.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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