[#11737] docs(core): add multi-node entity store cache invalidation design#11738
Draft
yuqi1129 wants to merge 3 commits into
Draft
[#11737] docs(core): add multi-node entity store cache invalidation design#11738yuqi1129 wants to merge 3 commits into
yuqi1129 wants to merge 3 commits into
Conversation
Code Coverage Report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Adds a design doc,
design-docs/entity-cache-multinode-changelog-design.md, proposing how to make the entity store cache (gravitino.cache.enabled) usable in multi-node deployments by invalidating it across nodes via the existingentity_change_logandEntityChangeLogPoller. It presents two options (coarse by-metalake vs. precise per-endpoint) with a recommendation, plus a consistency model and a coverage audit.Why are the changes needed?
Today the entity store cache only invalidates locally, so multi-node deployments must disable it, which hurts performance (Iceberg especially). This is design-only; no code behavior changes yet.
Fix: #11737
Does this PR introduce any user-facing change?
No. Documentation and design only.
How was this patch tested?
No code changes; not applicable. The doc passes the repo docs-style audit scripts.