hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13469) [branch-1.1] Procedure V2 - Make procedure v2 configurable in branch-1.1
Date Wed, 22 Apr 2015 19:56:59 GMT

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

Hudson commented on HBASE-13469:
--------------------------------

SUCCESS: Integrated in HBase-1.1.0RC0-JDK7 #2 (See [https://builds.apache.org/job/HBase-1.1.0RC0-JDK7/2/])
HBASE-13469 Procedure v2 - Make procedure v2 configurable in branch-1.1 (Stephen Yuan Jiang)
(matteo.bertozzi: rev 3eb8021e38b9e92976f97e2d0c9577d3cff380f3)
* hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/TableNamespaceManager.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/MasterQuotaManager.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterServices.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestProcedureConf.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java


> [branch-1.1] Procedure V2 - Make procedure v2 configurable in branch-1.1
> ------------------------------------------------------------------------
>
>                 Key: HBASE-13469
>                 URL: https://issues.apache.org/jira/browse/HBASE-13469
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master
>    Affects Versions: 1.1.0
>            Reporter: Enis Soztutar
>            Assignee: Stephen Yuan Jiang
>             Fix For: 1.1.0
>
>         Attachments: HBASE-13469.v2-branch-1.1.patch
>
>
> In branch-1, I think we want proc v2 to be configurable, so that if any non-recoverable
issue is found, at least there is a workaround. We already have the handlers and code laying
around. It will be just introducing the config to enable / disable. We can even make it dynamically
configurable via the new framework. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message