yuqi1129 commented on issue #11736: URL: https://github.com/apache/gravitino/issues/11736#issuecomment-5043032261
For #11737, closing this issue should distinguish the independently tracked failure modes: - PR #11739 addresses per-listener failure retry, but explicitly leaves the commit-order gap as an accepted limitation. Logging or documenting the gap is not prevention. - Add a deterministic test where transaction A obtains the lower ID, transaction B commits the higher ID first, the poller advances, and transaction A commits afterward. - Verify backlog draining beyond the 500-row batch, listener registration/startup ordering, and retention overrun behavior. - Expose lag age/count, listener errors, and last-success health signals. - Use bounded `expireAfterWrite` behavior so any missed invalidation cannot remain hot and stale forever. If commit-order prevention is intentionally deferred, #11737/#12019 should state the resulting consistency limit and define a clear cache clear/bypass fail-safe instead of claiming that every remote invalidation arrives within one poll interval. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
