[
https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186748#comment-16186748
]
Vincent Poon commented on PHOENIX-4219:
---------------------------------------
Still haven't figured this one out, but it seems to be a problem with the
scrutiny index query. If you run with totalRows=1200, it always fails on id
704, complaining that comment_count is null
But when I query the index table manually for that row, it looks fine
In fact, if I take the exact same index table query from the scrutiny, and
append it with where \":ORGANIZATION_ID\"='704' , the comment_count looks fine
So it seems to be a problem while iterating through the result set of the index
table query. At a certain point, it comes back with a null for the
comment_count, despite what's actually in the table.
Perhaps there's something wrong with the batching of the results.
> 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)
