[DOCS-10844] Stepdown command must take global lock in exclusive mode (SERVER-28544) Created: 27/Sep/17 Updated: 29/Oct/23 Resolved: 08/Feb/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.14 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kay Kim (Inactive) | Assignee: | Jonathan DeStefano |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 5 days ago | ||||||||
| Description |
| Comments |
| Comment by Githook User [ 09/Feb/18 ] |
|
Author: {'email': 'jonathan.destefano@10gen.com', 'name': 'jonathan', 'username': 'jdestefano-mongo'}Message: |
| Comment by Spencer Brody (Inactive) [ 22/Jan/18 ] |
|
It comes down to how you define when a node is "stepped down". Is it "stepped down" whenever it cannot accept writes, or only when it stops reporting itself as being in PRIMARY state? Either way, I think your assertion that the crux of the behavior change is that writes fail instead of blocking while waiting for secondaries to catch up is correct. If the writes being done are retryable, then the driver will automatically attempt to retry them against the new primary. |
| Comment by Jonathan DeStefano [ 22/Jan/18 ] |
|
After reviewing existing content and discussion with spencer I am led to believe a piece of the Documentation Request Summary is incorrect: "... if no secondaries catch up within the secondary catch up time period then the node will step back up automatically and start accepting writes again." I believe at this point of the procedure the primary has not yet stepped down. As per current documentation (which I believe to be correct): After which, it will be able to accept writes again. After a cursory search, I believe the only change required for this ticket is to update: |