[SERVER-25337] Remove global lock in configsvr commit{split/merge/migrate} chunk commands Created: 29/Jul/16 Updated: 05/Apr/17 Resolved: 17/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jess Fan | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-01-02 |
| Participants: |
| Description |
|
These instances of GlobalLock can be removed after 3.4 - they were only there for compatibility with 3.2 mongoses |
| Comments |
| Comment by Githook User [ 17/Jan/17 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: chunk commands |
| Comment by Spencer Brody (Inactive) [ 06/Jan/17 ] |
|
Because it can now synchronize on the less-expensive _kChunkOpLock ResourceMutex, now that there's no concern of a 3.2 mongos modifying the config.chunks collection out from under it. |
| Comment by Dianna Hohensee (Inactive) [ 06/Jan/17 ] |
|
Why do we want to get rid of the global lock for CommitChunkMigration? It's used to serialize commits, because the config server generates new ChunkVersion from the existing config.chunks data. |