-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying
-
Fully Compatible
-
v4.4, v4.2
-
Sharding 2020-03-23
-
18
The upserts performed by the $config.data.create() function may fail with a NoProgressMade error response from mongos due to a shard returning a CannotImplicitlyCreateCollection error response after the collection has been dropped.
const cmdRes = db.runCommand({ update: collName, updates: [{ q: {_id: i}, u: {$set: {a: i, b: this.nDocs - i, c: i, d: this.nDocs - i, e: "foo"}}, upsert: true }] });
We should add ErrorCodes.NoProgressMade to the $config.data.kAllowedErrors list.
- is related to
-
SERVER-32567 Replace queryoptimizer3.js with FSM test
- Closed