phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-4219) Index gets out of sync on HBase 1.x
Date Sun, 01 Oct 2017 06:17:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187263#comment-16187263
] 

James Taylor edited comment on PHOENIX-4219 at 10/1/17 6:16 AM:
----------------------------------------------------------------

I believe I've found the issue. Our RegionScanner implementation BaseScannerRegionObserver.RegionScannerHolder.nextRaw()
is returning partial results which confuses Phoenix. Need to think about the best way of turning
this off.

How wide are the rows in general for your test, @Vincent Poon?

[~sergey.soldatov] - this seems like another incarnation of PHOENIX-3112. We need to disable
this "feature" (and add a unit test for it). It completely breaks Phoenix when it happens.


was (Author: jamestaylor):
I believe I've found the issue. Our RegionScanner implementation BaseScannerRegionObserver.RegionScannerHolder.nextRaw()
is returning partial results which confuses Phoenix. Need to think about the best way of turning
this off.

> 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)

Mime
View raw message