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 760A6F595 for ; Fri, 29 Mar 2013 13:10:14 +0000 (UTC) Received: (qmail 4151 invoked by uid 500); 29 Mar 2013 12:58:53 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 3962 invoked by uid 500); 29 Mar 2013 12:58:47 -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 3681 invoked by uid 99); 29 Mar 2013 12:58:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 12:58:34 +0000 Date: Fri, 29 Mar 2013 12:58:34 +0000 (UTC) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-4621) additional logging to help diagnose slow QJM logSync 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-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617314#comment-13617314 ] Hudson commented on HDFS-4621: ------------------------------ Integrated in Hadoop-Hdfs-trunk #1358 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1358/]) HDFS-4621. Additional logging to help diagnose slow QJM syncs. Contributed by Todd Lipcon. (Revision 1461777) Result = FAILURE todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1461777 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/client/IPCLoggerChannel.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/client/QuorumCall.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/Journal.java > additional logging to help diagnose slow QJM logSync > ---------------------------------------------------- > > Key: HDFS-4621 > URL: https://issues.apache.org/jira/browse/HDFS-4621 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, qjm > Affects Versions: 2.0.3-alpha > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Priority: Minor > Fix For: 3.0.0, 2.0.5-beta > > Attachments: hdfs-4621.txt > > > I've been working on diagnosing an issue with a cluster which is seeing slow logSync calls occasionally to QJM. Adding a few more pieces of logging would help this: > - in the warning messages on the client side leading up to a timeout, include which nodes have responded and which ones are still pending > - on the server side, when we actually call FileChannel.force, log a warning if the sync takes longer than 1 second -- 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