[SERVER-36581] stepdown hook should retry replSetFreeze command on AutoReconnect error Created: 10/Aug/18 Updated: 10/Aug/18 Resolved: 10/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 4.1.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | DO NOT USE - Backlog - Test Infrastructure Group (TIG) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
In the stepdown hook, we issue a replSetFreeze command after replSetStepdown. The latter will cause the connection to the client to be terminated as a result of the node stepping down, but the termination may not happen until after the command returns, which means the next command that gets issued on the same connection, not the replSetStepDown command itself, will see an invalid connection and get an AutoReconnect error. |
| Comments |
| Comment by Robert Guo (Inactive) [ 10/Aug/18 ] |
|
The replSetStepDown command is not expected to return when it succeeds. |