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

Hudson commented on HBASE-22935:
--------------------------------

Results for branch branch-1
        [build #1035 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1035/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- Something went wrong running this stage, please [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1035//console].


(x) {color:red}-1 jdk7 checks{color}
-- Something went wrong running this stage, please [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1035//console].


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- Something went wrong running this stage, please [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1035//console].




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


> TaskMonitor warns MonitoredRPCHandler task may be stuck when it recently 
> started
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-22935
>                 URL: https://issues.apache.org/jira/browse/HBASE-22935
>             Project: HBase
>          Issue Type: Bug
>          Components: logging
>    Affects Versions: 3.0.0, 1.4.0, 1.5.0, 1.3.3, 2.0.0
>            Reporter: David Manning
>            Assignee: David Manning
>            Priority: Minor
>         Attachments: HBASE-22935.master.001.patch
>
>
> After settingĀ {{hbase.taskmonitor.rpc.warn.time}} to 180000, the logs show 
> WARN messages such as these
> {noformat}
> 2019-08-08 21:50:02,601 WARN  [read for TaskMonitor] monitoring.TaskMonitor - 
> Task may be stuck: RpcServer.FifoWFPBQ.default.handler=4,queue=4,port=60020: 
> status=Servicing call from <ip>:55164: Scan, state=RUNNING, 
> startTime=1563305858103, completionTime=-1, queuetimems=1565301002599, 
> starttimems=1565301002599, clientaddress=<ip>, remoteport=55164, 
> packetlength=370, rpcMethod=Scan
> {noformat}
> Notice that the first {{starttimems}} is far in the past. The second 
> {{starttimems}} and the {{queuetimems}} are much closer to the log timestamp 
> than 180 seconds. I think this is because the warnTime is initialized to the 
> time that MonitoredTaskImpl is created, but never updated until we write a 
> warn message to the log.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to