Skip to content

Correct phrasing of FAQ and add hash key mention #1116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Correct phrasing of FAQ and add hash key mention #1116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions source/faq/sharding.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -344,10 +344,12 @@ initially belong to the same chunk on a single shard. Although the
system will eventually divide this chunk and migrate its contents to
distribute data more evenly, at any moment the cluster can only direct
insert operations at a single shard. This can limit the throughput of
inserts. If most of your write operations are updates or read
operations rather than inserts, this limitation should not impact
your performance. However, if you have a high insert volume, this may
be a limitation.
inserts. If most of your operations are not inserts, this limitation
should not impact your performance. However, if you have a high insert
volume, this may be a limitation.

To address this issue, you can use a field with a value that stores
the hash of a key with an ascending value starting with 2.4.

Can shard key be in ascending order, like dates or timestamps?
--------------------------------------------------------------
Expand Down