[SERVER-61660] shutdownTimeoutMillisForSignaledShutdown is too short in migration tests Created: 19/Nov/21 Updated: 13/Dec/21 Resolved: 13/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Server Serverless 2021-11-29, Server Serverless 2021-12-13, Server Serverless 2021-12-27 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
We observed in a "debug" variant in the tenant_migration_terminate_primary_jscore_passthrough suite that the primary didn't have time to hand off to a caught-up secondary before the primary exceeded waitTimeMillis and died. The resulting error bubbled up to the JS test and caused a BF. Since waitTimeMillis was only 100, it's not surprising that secondaries might occasionally lag for too long in a debug build to permit a clean handoff. Let's increase it. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 13/Dec/21 ] |
|
Closing. Perhaps this is a misdiagnosis of the linked BF. |