Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 54332 invoked from network); 4 Mar 2010 01:07:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Mar 2010 01:07:58 -0000 Received: (qmail 8514 invoked by uid 500); 4 Mar 2010 01:07:49 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 8491 invoked by uid 500); 4 Mar 2010 01:07:49 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 8483 invoked by uid 99); 4 Mar 2010 01:07:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Mar 2010 01:07:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Mar 2010 01:07:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3D2B9234C4C4 for ; Thu, 4 Mar 2010 01:07:27 +0000 (UTC) Message-ID: <2126945082.52991267664847249.JavaMail.jira@brutus.apache.org> Date: Thu, 4 Mar 2010 01:07:27 +0000 (UTC) From: "Kannan Muthukkaruppan (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Created: (HBASE-2284) fsWriteLatency metric may be incorrectly reported MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org fsWriteLatency metric may be incorrectly reported -------------------------------------------------- Key: HBASE-2284 URL: https://issues.apache.org/jira/browse/HBASE-2284 Project: Hadoop HBase Issue Type: Bug Reporter: Kannan Muthukkaruppan Priority: Minor fsWriteLatency metric is computed by maintaining writeTime & writeOps in HLog. If an HLog.append() carries multiple edits, then "writeTime" is computed incorrectly for the subsequent edits because doWrite() is called for each of the edits with the same start time argument ("now"). This also causes a lot of false WARN spews to the log. Only one of the edits might have taken a long time, but every edit after that in a given HLog.append() operation will also raise these warning messages. {code} 2010-03-03 11:00:42,247 WARN org.apache.hadoop.hbase.regionserver.HLog: IPC Server handler 51 on 60020 took 1814ms appending an edit to hlog; editcount=302227 2010-03-03 11:00:42,247 WARN org.apache.hadoop.hbase.regionserver.HLog: IPC Server handler 51 on 60020 took 1814ms appending an edit to hlog; editcount=302228 2010-03-03 11:00:42,247 WARN org.apache.hadoop.hbase.regionserver.HLog: IPC Server handler 51 on 60020 took 1814ms appending an edit to hlog; editcount=302229 2010-03-03 11:00:42,247 WARN org.apache.hadoop.hbase.regionserver.HLog: IPC Server handler 51 on 60020 took 1814ms appending an edit to hlog; editcount=302230 2010-03-03 11:00:42,247 WARN org.apache.hadoop.hbase.regionserver.HLog: IPC Server handler 51 on 60020 took 1814ms appending an edit to hlog; editcount=302231 {code} Will submit a patch shortly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.