[
https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185148#comment-16185148
]
Vincent Poon commented on PHOENIX-4219:
---------------------------------------
Yea I've been looking and seeing weird things as well
- The test always seems to end with same number of data and index table rows.
When I examine the bad rows from the scrutiny output, there is one data row
without an index row, and there is an index row with bad covered col values, so
probably an extra index row for a given data table row.
- It doesn't seem to be a batching thing, because I get a failure even if I set
batch size to 1, or get rid of executeBatch() altogether and just use execute()
for each row.
> Index gets out of sync on HBase 1.x
> -----------------------------------
>
> Key: PHOENIX-4219
> URL: https://issues.apache.org/jira/browse/PHOENIX-4219
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.12.0
> Reporter: Vincent Poon
> Priority: Blocker
> Attachments: PHOENIX-4219_test.patch, PHOENIX-4219_test_v2.patch
>
>
> When writing batches in parallel with multiple background threads, it seems
> the index sometimes gets out of sync. This only happens on the master and
> 4.x-HBase-1.2.
> The tests pass for 4.x-HBase-0.98
> See the attached test, which writes with 2 background threads with batch size
> of 100.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
