[SERVER-15310] kill all operations before attempting stepdown Created: 18/Sep/14 Updated: 27/Oct/15 Resolved: 01/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Description |
|
Since stepdown requires a global shared lock, it will block waiting possibly a very long time if there are long running write operations with a document-level-locking storage engine. Such write operations could be things like map/reduce or index builds. We should kill those operations before attempting to enqueue the global shared lock. |
| Comments |
| Comment by Githook User [ 01/Dec/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |