You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Himanshu Gwalani (Jira)" <ji...@apache.org> on 2026/10/10 06:17:00 UTC

[jira] [Resolved] (PHOENIX-7802) Add replayState check to shouldTriggerFailover() for defense-in-depth

     [ https://issues.apache.org/jira/browse/PHOENIX-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Himanshu Gwalani resolved PHOENIX-7802.
---------------------------------------
    Resolution: Fixed

> Add replayState check to shouldTriggerFailover() for defense-in-depth
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-7802
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7802
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Himanshu Gwalani
>            Assignee: Himanshu Gwalani
>            Priority: Major
>             Fix For: PHOENIX-7562-feature, 5.4.0
>
>
> *Issue*
> If getFirstRoundToProcess() returns empty (degradation < ~69 sec), control skips the SYNCED_RECOVERY and goes directly to shouldTriggerFailover().
> {*}Note{*}: Existing safeguards (new files check, timing constraints) prevent data loss in production, but this fix protects against future edge cases.
> *Solution*
> Add replicationReplayState check to shouldTriggerFailover() in ReplicationLogDiscoveryReplay.java as a defense-in-depth improvement.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)