You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2012/10/24 02:20:12 UTC
[jira] [Updated] (HBASE-7039) Port HBASE-5914 Bulk assign regions
in the process of ServerShutdownHandler (and bugfix part of HBASE-6012) to
0.94
[ https://issues.apache.org/jira/browse/HBASE-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Shelukhin updated HBASE-7039:
------------------------------------
Description:
This is a major feature, so please -1 if you think it's too dangerous to port.
However, it's also a perf improvement for recovery.
The 2nd thing that HBASE-6012 addresses cannot be included without a breaking interface change (HRegionInterface openRegions doesn't return region states which are relied upon by the trunk code that is using protocol buffers API); or a non-breaking interface change with version-checking hackery to take advantage of it.
was:
This is a major feature, so please -1 if you think it's too dangerous to port.
However, it's also a perf improvement for recovery.
> Port HBASE-5914 Bulk assign regions in the process of ServerShutdownHandler (and bugfix part of HBASE-6012) to 0.94
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7039
> URL: https://issues.apache.org/jira/browse/HBASE-7039
> Project: HBase
> Issue Type: Task
> Affects Versions: 0.94.2
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
>
> This is a major feature, so please -1 if you think it's too dangerous to port.
> However, it's also a perf improvement for recovery.
> The 2nd thing that HBASE-6012 addresses cannot be included without a breaking interface change (HRegionInterface openRegions doesn't return region states which are relied upon by the trunk code that is using protocol buffers API); or a non-breaking interface change with version-checking hackery to take advantage of it.
--
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