[SERVER-11067] Use local db lock to save replica set [re]config Created: 07/Oct/13 Updated: 11/Jul/16 Resolved: 08/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Replication |
| Affects Version/s: | 2.4.4, 2.5.2 |
| Fix Version/s: | 2.5.3 |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | locking | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
Currently we take out a global write lock and flush the local database files before and after saving the replica set config. This is no longer needed and instead we can now use a local db write lock, and not flush the db repeatedly. In addition we can log the new config. |
| Comments |
| Comment by auto [ 08/Oct/13 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |