[SERVER-6846] Default Object Id can be random for reducing hotspots in sharding Created: 24/Aug/12 Updated: 24/Aug/12 Resolved: 24/Aug/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Trivial - P5 |
| Reporter: | mark nielsen | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
any |
||
| Participants: |
| Description |
|
The default Object Id is increasing approx sequentially. Out of the box, it would be nice to be able to use the object id in a sharded environment where the programmer doesn't have to worry about the shard key. Having an optional config setting to make the object id pseudo random would be nice. Just reverse the time portion of the object id or reverse the object id entirely. The correct thing to do is for the programmer to define the value of the object id, but this doesn't always happen. |
| Comments |
| Comment by mark nielsen [ 24/Aug/12 ] |
|
Awesome! I tried to look for this, didn't find it. Sorry for the repeat. |
| Comment by mark nielsen [ 24/Aug/12 ] |
|
Ah, couldn't find a way to close this ticket or mark it as a duplicate. |
| Comment by Eliot Horowitz (Inactive) [ 24/Aug/12 ] |
|
|