You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2026/10/09 21:19:00 UTC
[jira] [Updated] (PHOENIX-7989) Fix close-resurrection double-writer in ReplicationLogGroup
[ https://issues.apache.org/jira/browse/PHOENIX-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell updated PHOENIX-7989:
-----------------------------------------
Fix Version/s: PHOENIX-7562-feature
5.4.0
> Fix close-resurrection double-writer in ReplicationLogGroup
> -----------------------------------------------------------
>
> Key: PHOENIX-7989
> URL: https://issues.apache.org/jira/browse/PHOENIX-7989
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Tanuj Khurana
> Assignee: Tanuj Khurana
> Priority: Major
> Fix For: PHOENIX-7562-feature, 5.4.0
>
>
> close() removed the instance from INSTANCES at the top, before a multi-second disruptor drain. A concurrent get() during that window missed the cache and constructed a second live instance for the same shard, producing two writers (confirmed in a captured abort log).
> Remove from the cache only after teardown, in a finally so a throwing teardown step cannot strand a closed instance (which would break the active->standby->active re-promotion path without a JVM restart). The removal is value-specific (remove(key, this)) so a later instance for the same key is never clobbered. The closed flag is still set first, so a get() during the drain returns the still-closing instance whose append()/sync() fail fast rather than a fresh writer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)