[DOCS-1547] Change details around Tag Aware sharding and Chunks that span tags Created: 28/May/13 Updated: 30/Oct/23 Resolved: 17/Sep/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.4 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Thomas Boyd | 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, 20 weeks, 5 days ago |
| Description |
|
The write-up at http://docs.mongodb.org/manual/core/tag-aware-sharding/ raises the issue of chunks with data that belongs on two shards being put on the shard whose tag is the closest match. While this is technically correct, I believe we should point out that pre-splitting and manual migrations can keep this from happening. Otherwise tag-ware sharding is really of limited value. |
| Comments |
| Comment by auto [ 27/Sep/13 ] |
|
Author: {u'username': u'Zackrobat', u'name': u'Zack Brown', u'email': u'zack.brown@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| Comment by Sam Kleinman (Inactive) [ 06/Sep/13 ] |