You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2013/03/29 02:13:15 UTC
[jira] [Updated] (HBASE-8217) Port online region merge (HBASE-7403)
to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated HBASE-8217:
---------------------------------
Attachment: hbase-8217_v2.patch
Attaching backported patch. This depends on HBASE-8196.
A couple of changes from the original patch:
- RPC changes (obviously)
- AM.processRegionsInTransition() handles SPLITTING/SPLIT and MERGING/MERGE cases, while 0.94 AM does not handle SPLITTING/SPLIT states. I did not add the corresponding MERGE changes. Shall we open another issue for adding the SPLIT changes?
- CatalogJanitor is not exposed in 0.94 through RPC. Added some reflection code in test.
Rolling upgrades should work. I did not see a case which might cause a problem. However, obviously, you should not try to merge unless cluster is fully upgraded.
Unit tests seem good.
{code}
Results :
Tests run: 1333, Failures: 0, Errors: 0, Skipped: 13
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
{code}
> Port online region merge (HBASE-7403) to 0.94
> ---------------------------------------------
>
> Key: HBASE-8217
> URL: https://issues.apache.org/jira/browse/HBASE-8217
> Project: HBase
> Issue Type: New Feature
> Components: master, Region Assignment, regionserver
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.94.7
>
> Attachments: hbase-8217_v2.patch
>
>
> HBASE-7403 added online region merge, and there was some discussion about whether we can port this to 0.94.
> In this issue, we can discuss feasibility and decide one what way or the other. I actually have a patch on top of backported HBASE-7721.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira