[SERVER-34360] shard_identity_rollback.js has unreliable check for node crash Created: 06/Apr/18 Updated: 07/Feb/20 Resolved: 07/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Repl 2020-02-24 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 8 | ||||||||||||
| Description |
|
In shard_identity_rollback.js, we check that a node crashes by checking that establishing a connection throws. However, this can also throw when connections are closed due to entering ROLLBACK. Instead, we should wait for a ping command on the node to fail and check for a non-zero exit code, like we do in this test. |