[
https://issues.apache.org/jira/browse/HBASE-16586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497206#comment-15497206
]
Hudson commented on HBASE-16586:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1614 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/1614/])
HBASE-16586 Procedure v2 - Cleanup sched wait/lock semantic (matteo.bertozzi:
rev b6b72361b68634f15f8cf83738d89147633ac378)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/master/procedure/TestMasterProcedureScheduler.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/MasterProcedureScheduler.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/DispatchMergingRegionsProcedure.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/MasterProcedureEnv.java
> Procedure v2 - Cleanup sched wait/lock semantic
> -----------------------------------------------
>
> Key: HBASE-16586
> URL: https://issues.apache.org/jira/browse/HBASE-16586
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
> Affects Versions: 2.0.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Fix For: 2.0.0
>
> Attachments: HBASE-16586-v0.patch, HBASE-16586-v1.patch,
> HBASE-16586-v2.patch, HBASE-16586-v3.patch
>
>
> For some reason waitEvent() and waitRegion() had a mismatching return value.
> unity the wait semantic in being: return true we wait, false we don't wait.
> procedures using hasLock = waitRegion() should change to hasLock =
> !waitRegion(). at the moment we have only DispatchMergingRegionsProcedure
> using it (in master).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
