[ 
https://issues.apache.org/jira/browse/HBASE-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885732#comment-17885732
 ] 

Hudson commented on HBASE-2284:
-------------------------------

Results for branch master
        [build #1173 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1173/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1173/General_20Nightly_20Build_20Report/]








(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1173/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> fsWriteLatency metric may be incorrectly reported 
> --------------------------------------------------
>
>                 Key: HBASE-2284
>                 URL: https://issues.apache.org/jira/browse/HBASE-2284
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Kannan Muthukkaruppan
>            Assignee: Kannan Muthukkaruppan
>            Priority: Minor
>             Fix For: 0.20.4, 0.90.0
>
>         Attachments: 2284_0.20.patch
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to