Loading...

XML

Word

Printable

JSON

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Steps To Reproduce:
Hide

let rst = new ReplSetTest({nodes: 1}); rst.startSet(); let db = rst.nodes[0].getDB('local'); assert.commandWorked(db.runCommand({ isMaster: 1, "$clusterTime": { "clusterTime": Timestamp(1, 1), "signature": {"hash": BinData(0, "AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId": NumberLong(0)} } })); db.runCommand({ find: "oplog.rs", filter: {ts: {$gte: Timestamp(1520004466, 2)}}, tailable: true, oplogReplay: true, awaitData: true, maxTimeMS: 60000, batchSize: 13981010, term: 1, readConcern: {afterClusterTime: Timestamp(1, 1)} });
Show
let rst = new ReplSetTest({nodes: 1}); rst.startSet(); let db = rst.nodes[0].getDB('local'); assert.commandWorked(db.runCommand({ isMaster: 1, "$clusterTime": { "clusterTime": Timestamp(1, 1), "signature": {"hash": BinData(0, "AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId": NumberLong(0)} } })); db.runCommand({ find: "oplog.rs", filter: {ts: {$gte: Timestamp(1520004466, 2)}}, tailable: true, oplogReplay: true, awaitData: true, maxTimeMS: 60000, batchSize: 13981010, term: 1, readConcern: {afterClusterTime: Timestamp(1, 1)} });
Sprint:
Repl 2018-05-21, Repl 2018-06-04, Repl 2018-06-18
Linked BF Score:
60

We do not check if the node has a config before trying to satisfy the read concern, so we fail trying to wait for oplog visibility.

causes

SERVER-70785 data race on the _rsConfigState field inside waitUntilOpTimeForReadUntil

is duplicated by

SERVER-32940 ReplicationCoordinator waitUntilOpTimeForReadUntil should return NotYetInitialized when oplog has not been created.

related to

SERVER-35616 Oplog query on initial syncing node can cause segmentation fault

Participants:: Githook User, Judah Schvimer, Matthew Russotto, Spencer Brody