[
https://issues.apache.org/jira/browse/PHOENIX-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954275#comment-16954275
]
Lars Hofhansl commented on PHOENIX-5527:
----------------------------------------
So the difference is that in phase I you only set VERIFIED to false, and in
phase III you write the index row and set VERIFIED to true atomically, right?
I agree that alone does not affect correctness and would solve the replication
problem more elegantly.
Geoffrey is right on point #2 (and #3.) Let's not rush this in, but consider
this carefully.
I don't get the ts-1 part. You mean to say that the main table ts (and full row
ts) is as least 1ms later than the VERIFIED false update? That seems easy to
do... BUT we'd have to reason through concurrent writes.
Let's not delay 4.15.0 for this, though, we can change this in 4.15.1.
> Unverified index rows should not be deleted due to replication lag
> -------------------------------------------------------------------
>
> Key: PHOENIX-5527
> URL: https://issues.apache.org/jira/browse/PHOENIX-5527
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-5527.master.001.patch,
> PHOENIX-5527.master.002.patch
>
>
> The current default delete time for unverified index rows is 10 minutes. If
> an index table row is replicated before its data table row and the
> replication row is unverified at the time of replication, it can be deleted
> when it is scanned on the destination cluster. To prevent these deletes due
> to replication lag issues, we should increase the default time to 7 days.
> This value is configurable using the configuration parameter,
> phoenix.global.index.row.age.threshold.to.delete.ms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
