Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B216610813 for ; Tue, 11 Feb 2014 05:29:28 +0000 (UTC) Received: (qmail 32611 invoked by uid 500); 11 Feb 2014 05:29:27 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 32242 invoked by uid 500); 11 Feb 2014 05:29:21 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 32231 invoked by uid 99); 11 Feb 2014 05:29:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Feb 2014 05:29:20 +0000 Date: Tue, 11 Feb 2014 05:29:19 +0000 (UTC) From: "Kihwal Lee (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-5583) Make DN send an OOB Ack on shutdown before restaring MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897545#comment-13897545 ] Kihwal Lee commented on HDFS-5583: ---------------------------------- This jira depends on HDFS-5585. I will post a patch, which applies on top of HDFS-5585. > Make DN send an OOB Ack on shutdown before restaring > ---------------------------------------------------- > > Key: HDFS-5583 > URL: https://issues.apache.org/jira/browse/HDFS-5583 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Kihwal Lee > Assignee: Kihwal Lee > > Add an ability for data nodes to send an OOB response in order to indicate an upcoming upgrade-restart. Client should ignore the pipeline error from the node for a configured amount of time and try reconstruct the pipeline without excluding the restarted node. If the node does not come back in time, regular pipeline recovery should happen. > This feature is useful for the applications with a need to keep blocks local. If the upgrade-restart is fast, the wait is preferable to losing locality. It could also be used in general instead of the draining-writer strategy. -- This message was sent by Atlassian JIRA (v6.1.5#6160)