hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17699) Fix TestLockProcedure
Date Sat, 25 Feb 2017 13:15:44 GMT

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

stack commented on HBASE-17699:
-------------------------------

+1

In the MasterProcedureScheduler#clear, should you call the super#clear? Fix on commit.

Looking at the Interface, it says:

  /**
   * Removes all of the elements from the queue
   */

Should we clear table and server queue  and runqueues in the MasterProcedureScheduler when
#clear is called?


> Fix TestLockProcedure
> ---------------------
>
>                 Key: HBASE-17699
>                 URL: https://issues.apache.org/jira/browse/HBASE-17699
>             Project: HBase
>          Issue Type: Bug
>          Components: proc-v2
>            Reporter: Appy
>            Assignee: Appy
>            Priority: Blocker
>         Attachments: HBASE-17699.master.001.patch
>
>
> TestLockProcedure is failing consistently after HBASE-17605. It's interesting that HadoopQA
didn't report any test failures on that jira. Anyways, need to fix the test now.



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

Mime
View raw message