You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2021/04/08 19:17:00 UTC

[jira] [Commented] (HBASE-25749) Improved logging when interrupting active RPC handlers holding the region close lock (HBASE-25212 hbase.regionserver.close.wait.abort)

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

Andrew Kyle Purtell commented on HBASE-25749:
---------------------------------------------

[~dmanning] Ack, thank you

> Improved logging when interrupting active RPC handlers holding the region close lock (HBASE-25212 hbase.regionserver.close.wait.abort)
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-25749
>                 URL: https://issues.apache.org/jira/browse/HBASE-25749
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver, rpc
>    Affects Versions: 3.0.0-alpha-1, 1.7.0, 2.4.0
>            Reporter: David Manning
>            Assignee: Andrew Kyle Purtell
>            Priority: Minor
>
> HBASE-25212 adds an optional improvement to Close Region, for interrupting active RPC handlers holding the region close lock. If, after the timeout is reached, the close lock can still not be acquired, the regionserver may abort. It would be helpful to add logging for which threads or components are holding the region close lock at this time.
> Depending on the size of regionLockHolders, or use of any stack traces, log output may need to be truncated. The interrupt code is in HRegion#interruptRegionOperations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)