hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Yuan Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13469) [branch-1.1] Procedure V2 - Make procedure v2 configurable in branch-1.1
Date Wed, 15 Apr 2015 21:40:58 GMT

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

Stephen Yuan Jiang commented on HBASE-13469:

[~stack] I discussed with Enis about cleanup handler code - it requires a lot of changes (though
not complicated) to make both handler and procedure call the same method.  This is only for
1.1 release.  I think we should spend our energy to clean up handler code in 1.2 and make
procedure robust.  

The reason that we need it for 1.1 is due to the PV2 feature is too new and we are really
close to 1.1 release (< 4 weeks based on current schedule); we need to reduce risk for
1.1 release.  For 1.2+ - we have more time to test/fix issues, we should be ok to remove the
conf and handler code (I changed the title of this Jira only for 1.1).

> [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
>            Reporter: Enis Soztutar
>            Assignee: Stephen Yuan Jiang
>             Fix For: 1.1.0
> 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

View raw message