[
https://issues.apache.org/jira/browse/PHOENIX-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319816#comment-14319816
]
Rajeshbabu Chintaguntla commented on PHOENIX-1634:
--------------------------------------------------
[~mujtabachohan]
>From the logs you have shared we can see explicit move has called on data
>region so there is colocation mismatches. I will handle this case in
>PHOENIX-1658.
{code}
2015-02-12 15:57:46,712 INFO [FifoRpcScheduler.handler1-thread-12]
master.HMaster: Client=hadoop//10.0.53.56 move
hri=PERFORMANCE_1000000,,1423785445848.1b825954237502c720ae8f853e0706a0.,
src=vampire3.internal.salesforce.com,60020,1423785280994,
dest=vampire1.internal.salesforce.com,60020,1423785300193, running balancer
{code}
{code}
2015-02-12 15:57:54,561 INFO [PriorityRpcServer.handler=4,queue=0,port=60020]
regionserver.HRegionServer: Close 1b825954237502c720ae8f853e0706a0, via zk=yes,
znode version=0, on vampire1.internal.salesforce.com,60020,1423785300193
2015-02-12 15:57:54,562 DEBUG [RS_CLOSE_REGION-vampire3:60020-1]
handler.CloseRegionHandler: Processing close of
PERFORMANCE_1000000,,1423785445848.1b825954237502c720ae8f853e0706a0.
2015-02-12 15:57:54,564 DEBUG [RS_CLOSE_REGION-vampire3:60020-1]
regionserver.HRegion: Closing
PERFORMANCE_1000000,,1423785445848.1b825954237502c720ae8f853e0706a0.: disabling
compactions & flushes
{code}
[~jamestaylor]
I will handle the two scenarios you have mentioned above and upload patch.
Thanks.
> LocalIndexSplitter prevents region from auto split
> --------------------------------------------------
>
> Key: PHOENIX-1634
> URL: https://issues.apache.org/jira/browse/PHOENIX-1634
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.3
> Reporter: Mujtaba Chohan
> Assignee: Rajeshbabu Chintaguntla
> Attachments: PHOENIX-1634.patch, logs.zip, performance.py
>
>
> Local index is *not* created for a multi-tenant table however empty HBase
> table is created in advance for local index. With data upserted in the
> multi-tenant table, after multiple successive auto-splits when region tries
> to split again on another region server, LocalIndexSplitter prevents
> auto-split from happening. [~rajesh23] Please see the log below. Thanks
> [~apurtell] and [~jamestaylor] for narrowing down this issue.
> {code}
> WARN org.apache.hadoop.hbase.regionserver.LocalIndexSplitter: Index region
> corresponindg to data region
> MYSCHEMA.MY_MULTITENANT_TABLE,,1422663910075.db3861e02b58e21b5383704375539ee5.
> not in the same server. So skipping the split.
> 2015-01-31 04:48:53,532 INFO
> org.apache.hadoop.hbase.regionserver.SplitRequest: Running rollback/cleanup
> of failed split of
> MYSCHEMA.MY_MULTITENANT_TABLE,,1422663910075.db3861e02b58e21b5383704375539ee5.;
> Coprocessor bypassing region
> MYSCHEMA.MY_MULTITENANT_TABLE,,1422663910075.db3861e02b58e21b5383704375539ee5.
> split.
> java.io.IOException: Coprocessor bypassing region
> MYSCHEMA.MY_MULTITENANT_TABLE,,1422663910075.db3861e02b58e21b5383704375539ee5.
> split.
> at
> org.apache.hadoop.hbase.regionserver.SplitTransaction.createDaughters(SplitTransaction.java:309)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransaction.execute(SplitTransaction.java:655)
> at org.apache.hadoop.hbase.regionserver.SplitRequest.run(SplitRequest.java:84)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
