[SERVER-11068] Use local db lock to save replica set [re]config Created: 07/Oct/13 Updated: 30/Oct/13 Resolved: 07/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Replication |
| Affects Version/s: | 2.4.4, 2.5.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | locking | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 Scott Hernandez (Inactive) [ 07/Oct/13 ] |
|
dup of |