[ 
https://issues.apache.org/jira/browse/HBASE-14306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yu Li updated HBASE-14306:
--------------------------
    Description: 
There're multiple issues in RegionGroupingProvider, including:
* The provider cache in it is using byte array as the key of ConcurrentHashMap, 
which is not right (the reason is 
[here|http://stackoverflow.com/questions/1058149/using-a-byte-array-as-hashmap-key-java])

* It's using IdentityGroupingStrategy to get group and use it as key of the 
cache, which means the cache will include an entry for each region. This is 
especially unnecessary when using BoundedRegionGroupingProvider

I would suggest to change BoundedRegionGroupingProvider from a *provider* to a 
pluggable *strategy*, which will make the whole picture much more clear.

For more details, please refer to the patch

  was:
There're multiple issues in RegionGroupingProvider, including:
# The provider cache in it is using byte array as the key of ConcurrentHashMap, 
which is not right (the reason is 
[here|http://stackoverflow.com/questions/1058149/using-a-byte-array-as-hashmap-key-java])

# It's using IdentityGroupingStrategy to get group and use it as key of the 
cache, which means the cache will include an entry for each region. This is 
especially unnecessary when using BoundedRegionGroupingProvider

I would suggest to change BoundedRegionGroupingProvider from a *provider* to a 
pluggable *strategy*, which will make the whole picture much more clear.

For more details, please refer to the patch


> Refine RegionGroupingProvider: fix issues and make it more scalable
> -------------------------------------------------------------------
>
>                 Key: HBASE-14306
>                 URL: https://issues.apache.org/jira/browse/HBASE-14306
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>            Reporter: Yu Li
>            Assignee: Yu Li
>
> There're multiple issues in RegionGroupingProvider, including:
> * The provider cache in it is using byte array as the key of 
> ConcurrentHashMap, which is not right (the reason is 
> [here|http://stackoverflow.com/questions/1058149/using-a-byte-array-as-hashmap-key-java])
> * It's using IdentityGroupingStrategy to get group and use it as key of the 
> cache, which means the cache will include an entry for each region. This is 
> especially unnecessary when using BoundedRegionGroupingProvider
> I would suggest to change BoundedRegionGroupingProvider from a *provider* to 
> a pluggable *strategy*, which will make the whole picture much more clear.
> For more details, please refer to the patch



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

Reply via email to