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

Hudson commented on HBASE-18091:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3072 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/3072/])
HBASE-18091 Added API for getting who currently holds a lock on (stack: rev 
837bb9ece796aee9bc1f82ec45414ea52ac33f80)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/ProcedureScheduler.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/MasterProcedureScheduler.java
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/SimpleProcedureScheduler.java


> Add API for who currently holds a lock on namespace/ table/ region and log 
> when state is LOCK_EVENT_WAIT
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18091
>                 URL: https://issues.apache.org/jira/browse/HBASE-18091
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2
>            Reporter: Umesh Agashe
>            Assignee: Umesh Agashe
>             Fix For: 2.0.0
>
>         Attachments: HBASE-18091.master.001.patch, 
> HBASE-18091.master.002.patch, HBASE-18091.master.002.patch
>
>
> Add API for who currently holds a lock on namespace/ table/ region and log 
> message when state is LOCK_EVENT_WAIT



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to