[
https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073938#comment-16073938
]
Andrew Purtell commented on HBASE-18248:
----------------------------------------
There is a separate setting for RPC tasks because that's what we really care
about and want to dump debug info into the logs about if they get stuck.
Honestly I don't care about other task types. We could restrict this change to
them.
I can add a default of 0 or -1 that says never warn so its completely optional.
Another option is make a new subclass for compaction tasks like there is for
RPC tasks and separate configuration options for them.
> Warn if monitored task has been tied up beyond a configurable threshold
> -----------------------------------------------------------------------
>
> Key: HBASE-18248
> URL: https://issues.apache.org/jira/browse/HBASE-18248
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2
>
> Attachments: HBASE-18248-branch-1.3.patch,
> HBASE-18248-branch-1.3.patch, HBASE-18248-branch-1.patch,
> HBASE-18248-branch-1.patch, HBASE-18248-branch-2.patch,
> HBASE-18248-branch-2.patch, HBASE-18248.patch, HBASE-18248.patch
>
>
> Warn if monitored task has been tied up beyond a configurable threshold. We
> especially want to do this for RPC tasks. Use a separate threshold for
> warning about stuck RPC tasks versus other types of tasks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
