Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 088C5D7FB for ; Mon, 12 Nov 2012 19:13:14 +0000 (UTC) Received: (qmail 88800 invoked by uid 500); 12 Nov 2012 19:13:12 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 88414 invoked by uid 500); 12 Nov 2012 19:13:12 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 88219 invoked by uid 99); 12 Nov 2012 19:13:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 19:13:12 +0000 Date: Mon, 12 Nov 2012 19:13:12 +0000 (UTC) From: "Todd Lipcon (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: <2031096876.102051.1352747592297.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HDFS-4176) EditLogTailer should call rollEdits with a timeout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Todd Lipcon created HDFS-4176: --------------------------------- Summary: EditLogTailer should call rollEdits with a timeout Key: HDFS-4176 URL: https://issues.apache.org/jira/browse/HDFS-4176 Project: Hadoop HDFS Issue Type: Bug Components: ha, name-node Affects Versions: 2.0.2-alpha, 3.0.0 Reporter: Todd Lipcon When the EditLogTailer thread calls rollEdits() on the active NN via RPC, it currently does so without a timeout. So, if the active NN has frozen (but not actually crashed), this call can hang forever. This can then potentially prevent the standby from becoming active. This may actually considered a side effect of HADOOP-6762 -- if the RPC were interruptible, that would also fix the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira