Update sharding documentation following Meilisearch's automatic splitting of documents #3345
+141
−20
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
dureuill
force-pushed
the
EXP-257-sharding-split-docs
branch
from
58e6f67 to
e4d259b
Compare
…ment the automatic sharding
curquiza
reviewed
Aug 25, 2025
curquiza
reviewed
Aug 25, 2025
|
|
||
| ## Add documents | ||
|
|
||
| Send documents to any instance to have them replicated to the other instances. |
There was a problem hiding this comment.
I remembered we said people should send to one shard, but my memory is not great today 😂
There was a problem hiding this comment.
the answer is a bit subtle here.
- In v1.19, as long as the client waits for the engine's response before sending another task, they can send their documents to any instance.
- However, we might not keep this property in future versions (to be able to dynamically update the network topology), so it might be best to already advise using a single node for writes.
The message about sharding was not appearing because I had used the NoticeTag as a wrapping tag, which it isn't.
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.
Pull Request
Related issue
Fixes https://linear.app/meilisearch/issue/EXP-257/update-sharding-guide-following-splitting-of-documents (internal)
What does this PR do?
networkandremoteobjects with the new fieldstaskobject with the newnetworkfieldPR checklist
Please check if your PR fulfills the following requirements:
Thank you so much for contributing to Meilisearch!