docs(master): add metadata service design summary (#951) - #1451
Draft
yangcx000 wants to merge 1 commit into
Draft
Conversation
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.
Summary
Add a Chinese review document that summarizes Curvine metadata-service behavior and proposes an evolution path toward a stateless MDS with metadata storage separated by
WriteType.The document distinguishes current implementation facts from proposed design directions. It is intentionally submitted as a draft for community discussion; the per-operation protocol design in Chapter 4 remains to be completed after the high-level direction is reviewed.
Issue Describe / Design
Related to #951 and #1321.
The current Master keeps CacheMode soft-state metadata and FsMode/native authoritative metadata in the same in-memory tree, lock domain, RocksDB store, and Raft journal. This couples request-serving capacity, metadata capacity, and persistence policy even though the two metadata classes have different consistency and durability requirements.
The document:
This PR proposes a discussion document only. It does not change runtime behavior or commit the project to a specific storage backend.
Changes
metadata-service-summary.mdTest verified
git diff --no-index --check /dev/null metadata-service-summary.mdDependencies