[
https://issues.apache.org/jira/browse/PHOENIX-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325003#comment-14325003
]
Mujtaba Chohan commented on PHOENIX-1634:
-----------------------------------------
[~rajeshbabu], [~jamestaylor] Using HBase 0.98.10, there is still one important
upgrade cases still failing when Phoenix gets upgraded from 4.2.1 to 4.3.0
SUCCESS CASES:
New multi-tenant table created/split in Phoenix 4.3.0
New multi-tenant table created/split in Phoenix 4.2.1
FAILURE CASE:
Steps:
1. New multi-tanant table created with Phoenix 4.2.1 (not split and consists of
a single region only)
2. Server upgraded to Phoenix 4.3.0.
3. Split triggered on multi-tenant table
4. Splits fails with the following exception:
{code}
[regionserver60020-splits-1424210580270] regionserver.SplitRequest: Running
rollback/cleanup of failed split of
PERFORMANCE_1000000,,1424210351670.9c064bb33e31425ade5346494a5ccd51.;
Coprocessor bypassing region
PERFORMANCE_1000000,,1424210351670.9c064bb33e31425ade5346494a5ccd51. split.
java.io.IOException: Coprocessor bypassing region
PERFORMANCE_1000000,,1424210351670.9c064bb33e31425ade5346494a5ccd51. split.
at
org.apache.hadoop.hbase.regionserver.SplitTransaction.createDaughters(SplitTransaction.java:313)
{code}
> 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
> Fix For: 5.0.0, 4.3
>
> Attachments: PHOENIX-1634.patch, PHOENIX-1634_v2.patch,
> PHOENIX-1634_v3.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)
