[
https://issues.apache.org/jira/browse/PHOENIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552470#comment-17552470
]
Kadir Ozdemir commented on PHOENIX-6702:
----------------------------------------
I did some more debugging with [~vjasani]. We could reproduce the problem with
1 thread instead of using 5 threads, but we have to increase the number
mutations in the test from 10000 to 50000 per thread. This proves that it is
not the concurrent mutations but the number of versions of a row matters. We
think that the problem is with HBASE 25709 as [~richardantal] pointed out. It
is the handling of large rows during splits by HBase introduced by HBASE 25709
is likely the root cause. To prove this, we pre slit the index table using
{code:java}
conn.createStatement().execute("CREATE INDEX " + indexName + " ON " + tableName
+ "(v1) INCLUDE(v2, v3) SPLIT ON (1, 5, 10, 15, 20)"); {code}
and the problem went away.
> ConcurrentMutationsExtendedIT and PartialIndexRebuilderIT fail on Hbase
> 2.4.11+
> -------------------------------------------------------------------------------
>
> Key: PHOENIX-6702
> URL: https://issues.apache.org/jira/browse/PHOENIX-6702
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.2.0, 5.1.3
> Reporter: Istvan Toth
> Assignee: Kadir Ozdemir
> Priority: Blocker
> Fix For: 5.2.0
>
> Attachments: bisect.sh
>
>
> On my local machine
> ConcurrentMutationsExtendedIT.testConcurrentUpserts failed 6 out 10 times
> while PartialIndexRebuilderIT.testConcurrentUpsertsWithRebuild failed 10 out
> of 10 times with HBase 2.4.11 (the default build)
> The same tests succeeded 3 out of 3 times with HBase 2.3.7.
> Either HBase 2.4 has a bug, or our compatibility modules need to be fixed.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
