[SERVER-15633] ShardingState::doRefreshMetadata should take a more granular lock than exclusive db Created: 13/Oct/14 Updated: 19/Nov/14 Resolved: 27/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.7.7 |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
It should not need to take exclusive lock on DB once the collection level locking implementation is ready. |
| Comments |
| Comment by Githook User [ 27/Oct/14 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |