Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Gone away
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:

Sprint:
Sharding 2020-04-20
Linked BF Score:
0
Confidence Status:
None
Work Order:
0

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

In testing changes for ~~SERVER-31670~~, setting secondaries to have zero votes causes some tests in the causally consistent passthrough suites to fail complaining that the afterClusterTime sent to a secondary is after the clusterTime on the secondary.

As a temporary fix, we are not giving secondaries zero votes in those suites. These failures should be investigated, and the voting_secondaries: true options should be removed from the causally_consistent*.yml configs.

depends on

SERVER-34597 shardedcluster.py does not wait correctly on shards initialization

Closed

is related to

SERVER-31670 Change replica set fixture used by replica_sets_jscore_passthrough to make its secondary have zero votes

Closed

SERVER-32775 Investigate afterClusterTime error in causally consistent suite with 0 vote secondaries

Closed

Assignee:: Max Hirschhorn

Reporter:: Kevin Albertson

Participants:: Kevin Albertson, Kevin Duong, Max Hirschhorn

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: Jan 05 2018 10:43:59 PM UTC

Updated:: Oct 27 2023 08:43:43 PM UTC

Resolved:: Apr 17 2020 12:40:59 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates