[
https://issues.apache.org/jira/browse/PHOENIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547024#comment-17547024
]
Geoffrey Jacoby commented on PHOENIX-6702:
------------------------------------------
[~kozdemir]- this is the issue I mentioned to you earlier today. I looked at
this some yesterday and confirmed that the failure seems to be genuine. At the
end of the concurrent upsert test we're doing an IndexScrutiny (the non-MR
kind) and finding at least one row that was present in the _data_ table but
missing in the index table, which should never happen in a case with no deletes
(which is the case for this test).
The HBase JIRA that [~stoty] links above changed the HBase scanners to return
early in some circumstances; I'm wondering if there's a hidden assumption
somewhere in Phoenix now that we get the full page back with the option of more
rows, or a partial with no extra rows. I didn't see anything suspicious looking
in the GlobalIndexScanner and PagedRegionScanner.
> 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
> 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)
