You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "loserwang1024 (via GitHub)" <gi...@apache.org> on 2026/07/14 13:02:14 UTC

[I] [client] KV snapshot lease operations fail with stale coordinator metadata after upgrade [fluss]

loserwang1024 opened a new issue, #3652:
URL: https://github.com/apache/fluss/issues/3652

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
   
   
   ### Fluss version
   
   0.9.0 (latest release)
   
   ### Please describe the bug 🐞
   
   During a Fluss cluster upgrade, a running Flink job may fail in its enumerator with the following exception:
   ```java
   org.apache.flink.util.FlinkRuntimeException: Failed to get table snapshot
   ```
   
   The enumerator uses KV snapshot leases to prevent snapshots from being removed while they are being scanned. After the CoordinatorServer is restarted or its address changes during an upgrade, the client may still cache the old coordinator address.
   
   Read-only Admin APIs were made retryable in #3390. When a read request fails with a retriable network exception, the client refreshes its cluster metadata and retries the request against the updated server address.
   
   
   **However, the regular AdminGateway also contains write operations such as createTable, dropTable, and createDatabase.** These operations are not necessarily idempotent. If an operation succeeds on the server but its response is lost, automatically retrying it may execute the mutation twice. For this reason, the write gateway was intentionally excluded from the retry mechanism in #3390.
   
   KV snapshot lease operations are special. They are designed to be safe when the same request is executed repeatedly:
   * ACQUIRE_KV_SNAPSHOT_LEASE
   * RELEASE_KV_SNAPSHOT_LEASE
   * DROP_KV_SNAPSHOT_LEASE
   Therefore, these operations can refresh stale coordinator metadata and retry after a retriable network failure without exposing the coordinator restart to the Flink enumerator.
   
   
   
   ### Solution
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [client] KV snapshot lease operations fail with stale coordinator metadata after upgrade [fluss]

Posted by "loserwang1024 (via GitHub)" <gi...@apache.org>.
loserwang1024 closed issue #3652: [client] KV snapshot lease operations fail with stale coordinator metadata after upgrade
URL: https://github.com/apache/fluss/issues/3652


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org