You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/04/14 21:58:00 UTC
[jira] [Updated] (SPARK-56476) Fix invalid stamp error when upgrading read store to write store
[ https://issues.apache.org/jira/browse/SPARK-56476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated SPARK-56476:
-----------------------------------
Labels: pull-request-available (was: )
> Fix invalid stamp error when upgrading read store to write store
> ----------------------------------------------------------------
>
> Key: SPARK-56476
> URL: https://issues.apache.org/jira/browse/SPARK-56476
> Project: Spark
> Issue Type: Task
> Components: Structured Streaming
> Affects Versions: 4.2.0
> Reporter: B. Micheal Okutubo
> Priority: Major
> Labels: pull-request-available
>
> A task does two separate provider lookups from loadedProviders. The read phase gets provider P1 and acquires a stamp. The write phase looks up the provider again. Between the two lookups, another thread can remove P1 from loadedProviders.
> This happens when maintenance detects P1 as inactive via verifyIfStoreInstanceActive, or when another task's getStateStoreProvider receives providerIdsToUnload from the coordinator. The write phase then creates a new provider P2 via getOrElseUpdate. P2's state machine never issued P1's stamp, so upgradeReadStoreToWriteStore fails with StateStoreInvalidStamp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org