-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding, Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
v4.0, v3.6
-
Sharding 2018-10-08
-
20
When a primary steps down, it interrupts all ongoing user operations. If a command is currently executing JavaScript (like an eval or find with $where), its MozJS scope will be marked as killed and return ErrorCodes::Interrupted. This is expected / desired behavior for a stepdown, so the stepdown passthroughs should be resilient to this error code / message combination. The auto_retry_on_network_error.js override should be updated to retry on this response.
This is separate from SERVER-32565, which tracks adding retries on JS engine internal errors, which may not be desired behavior.
- is related to
-
SERVER-32565 Stepdown suites should tolerate js engine errors
- Closed