You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Priyank Porwal (Jira)" <ji...@apache.org> on 2019/10/14 16:59:00 UTC
[jira] [Commented] (PHOENIX-5527) Unverified index rows should not
be deleted due to replication lag
[ https://issues.apache.org/jira/browse/PHOENIX-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951156#comment-16951156 ]
Priyank Porwal commented on PHOENIX-5527:
-----------------------------------------
+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
> Attachments: PHOENIX-5527.master.001.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)