[DOCS-1342] Write Scaling docs should mention hashed shard key Created: 05/Apr/13  Updated: 26/Sep/13  Resolved: 12/Sep/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: James Wahlin Assignee: Zack Brown
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 10 years, 22 weeks, 5 days ago

 Description   

Our write scaling documentation currently states:

Typically, a computed shard key that has some amount of “randomness,” such as ones that include a cryptographic hash (i.e. MD5 or SHA1) of other content in the document, will allow the cluster to scale write operations. However, random shard keys do not typically provide query isolation, which is another important characteristic of shard keys.

This should be updated to refer to our hashed sharding docs. Note that I came to this page from the high randomness section of the "Select a Shard Key" page.



 Comments   
Comment by auto [ 13/Sep/13 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-1342: edits
Branch: master
https://github.com/mongodb/docs/commit/8ad5c147142e347b5a85ce0823f0825d81c783bd

Comment by auto [ 13/Sep/13 ]

Author:

{u'username': u'Zackrobat', u'name': u'Zack Brown', u'email': u'zack.brown@10gen.com'}

Message: DOCS-1342: Write Scaling docs should mention hashed shard key

Signed-off-by: Sam Kleinman <samk@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/d8ede209a46902188cb250c034140d30ee6240a4

Comment by Zack Brown [ 23/Aug/13 ]

From tychoish:

http://docs.mongodb.org/manual/tutorial/choose-a-shard-key/ should have a more explicit mention of hashed sharding

and

the point about the sharding-internals page should be applied to the new home for that content which is here: http://docs.mongodb.org/manual/core/sharding-shard-key/#write-scaling

#write-scaling

Generated at Thu Feb 08 07:40:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.