Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.15, 4.0.13, 4.2.1, 4.3.1
Affects Version/s: 3.4.16, 3.6.6, 4.0.0, 4.1.1
Component/s: Sharding
Labels:
- sharding-wfbf-day

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.2, v4.0, v3.6
Sprint:
Sharding 2018-08-13, Sharding 2018-08-27, Sharding 2019-09-23, Sharding 2019-10-07
Linked BF Score:
29
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

The call to restart() waits to connect to the restarted node by default, but in this case the node is expected to crash after starting up, so the call to restart is racy and can fail if the node crashes before restart() is able to connect to it.

The test should pass {waitForConnect: false} as the options object to this call to restart.

is duplicated by

SERVER-34360 shard_identity_rollback.js has unreliable check for node crash

Closed

Assignee:: Janna Golden
Reporter:: Esha Maharishi (Inactive)
Participants:: Esha Maharishi, Githook User, Janna Golden
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 20 2018 07:16:42 PM UTC
Updated:: Oct 29 2023 10:29:41 PM UTC
Resolved:: Sep 30 2019 09:44:39 PM UTC
Confidence Status Last Update:: 23/Sep/19 6:43 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates