[
https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185178#comment-16185178
]
Vincent Poon commented on PHOENIX-4219:
---------------------------------------
It seems to be a problem handling certain input.
It's more a function of totalRows than nBatches, nRowsPerBatch, nThreads. If I
play with any combination of the variables such that totalRows = 1200 , I
always get a failure, with the id of the orphaned data row always being the
same.
If totalRows is 1100 or less, the test always seems to pass.
The id is sequential, and the random number generator has a seed of 0. So the
input will always be the same from run to run. Something in the input past
1200 totalRows is causing things to fail.
However if I use a totalRows greater than 1200, the id of the orphaned row
changes... (though stays the same frrom run to run keeping totalRows constant)
> 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)
