Summary

What is the problem or use case, what are we trying to achieve?

This spec test is failing on latest sharded clusters

CRUD unified aggregate-out-readConcern readConcern available with out stage:

 
MongoServerError: PlanExecutor error during aggregation :: caused by :: failed while running command \{ internalRenameIfOptionsAndIndexesMatch: 1, from: "crud-v2.tmp.agg_out.20aa8895-2d27-49ac-ae5c-9fd62b3ba9f7", to: "crud-v2.other_test_collection", collectionOptions: {}, indexes: [ { v: 2, key: { _id: 1 }, name: "_id_" } ], writeConcern: \{ w: "majority", wtimeout: 0, provenance: "implicitDefault" } } :: caused by :: Request sent without attaching database version

Motivation

Who is the affected end user?

Drivers engineers

Who are the stakeholders?

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Is this ticket have any functional impact, or is it just test improvements?

Cast of Characters

Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders:

Channels & Docs

Slack Channel

[Scope Document|some.url]

[Technical Design Document|some.url]