Timeline for MongoDB - Clarification on choosing randomly distributed shard key
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 7, 2020 at 19:36 | history | suggested | CommunityBot | CC BY-SA 4.0 |
description highlight
|
| Sep 7, 2020 at 6:22 | review | Suggested edits | |||
| S Sep 7, 2020 at 19:36 | |||||
| Sep 22, 2017 at 23:00 | vote | accept | S.D. | ||
| Nov 23, 2016 at 23:12 | comment | added | S.D. | This is from one of the books I was reading "MongoDB: The Definitive Guide, Second Edition" Part IV sharding - Chapter -15 (Shard key Strategies)> It doesn't follow any context but here is the complete conclusion ... "The only downside to randomly distributed shard keys is that MongoDB isn’t efficient at randomly accessing data beyond the size of RAM. However, if you have the capacity or don’t mind the performance hit, random keys nicely distribute load across your cluster." | |
| Nov 23, 2016 at 23:09 | answer | added | Adam Harrison | timeline score: 2 | |
| Nov 23, 2016 at 22:58 | comment | added | Adam Harrison | Where did you read this? Context may provide information as to why this was said. | |
| Nov 23, 2016 at 21:56 | history | asked | S.D. | CC BY-SA 3.0 |