[SERVER-5283] other threads can see partially sharded chunkmanager Created: 11/Mar/12 Updated: 11/Jul/16 Resolved: 12/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
In between when sharding is enabled and the first chunks are created, it's possible for another thread on the same mongos to detect the collection as sharded but with no chunks. |
| Comments |
| Comment by Greg Studer [ 12/Jun/12 ] |
|
Explicitly fixed in 2.1.2. See DBConfig::CollectionInfo::shard(). Other race conditions on collection sharding remain, however. |
| Comment by Ian Whalen (Inactive) [ 17/May/12 ] |
|
@greg do you have any idea of why this is happening? |