Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.4.15, 3.5.13
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:
None

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

v3.4
Sprint:
Repl 2017-09-11
Confidence Status:
None
Work Order:
3

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

When waiting for background index builds to complete, ReplSetTest.checkReplicaSet() passes a

{w: all}

writeConcern with every collMod command invocation. This may not be necessary given that the function eventually calls ReplSetTest.awaitReplication() here:

https://github.com/mongodb/mongo/blob/1dc2afc8b5ce09d88535049df2ad72adc0434cc8/src/mongo/shell/replsettest.js#L1177

is depended on by

SERVER-30371 Separate renameCollection across DB commands into individual oplog entries

Closed

is duplicated by

SERVER-33498 ReplSetTest.checkReplicaSet fails when run against a config server replica set.

Closed

is related to

SERVER-24506 Support views in cloner & DataReplicator/DatabaseCloner

Closed

SERVER-25496 the validate hook will not work with older versions of mongod

Closed

SERVER-28989 Avoid dropping dummy database in ReplSetTest.prototype.checkReplicaSet()

Closed

Assignee:: Benety Goh
Reporter:: Benety Goh
Participants:: Benety Goh, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Aug 30 2017 07:14:06 PM UTC
Updated:: Oct 30 2023 11:13:55 PM UTC
Resolved:: Aug 30 2017 10:18:51 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates