[
https://issues.apache.org/jira/browse/PHOENIX-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961727#comment-16961727
]
Kadir OZDEMIR commented on PHOENIX-5527:
----------------------------------------
[~gjacoby], [~larsh], I have reopened this, and posted a PR and a very short
patch (after PHOENIX-5539 and PHOENIX-5540 for writing full index rows at phase
3). I have also addressed the very rare situation where data table (phase2) and
full index rows (phase 3) updates complete in less than 1 ms, by sleeping extra
1ms when this happens.
> 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, PHOENIX-5527.master.003.patch,
> PHOENIX-5527.master.004.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
