Loading...

XML

Word

Printable

JSON

Assigned Teams:

Storage Execution
Operating System:
ALL
Steps To Reproduce:

Hide

Version: 7.0.5

> db.createCollection( "weather", { timeseries:
{ timeField: "timestamp", metaField: "metadata" }
})
{ ok: 1 }
> db.adminCommand({shardCollection: 'test.weather', key: {_id: 1}, collectionUUID: UUID()} )

MongoServerError: Taking test.weather lock for timeseries is not allowed

Show
Version: 7.0.5 > db.createCollection( "weather", { timeseries: { timeField: "timestamp", metaField: "metadata" } }) { ok: 1 } > db.adminCommand({shardCollection: 'test.weather', key: {_id: 1}, collectionUUID: UUID()} ) MongoServerError: Taking test.weather lock for timeseries is not allowed

This issue does not appear in the most recent versions of 8.0, and the goal of this ticket is to identify and request the necessary backport.

It's imperative that CollectionUUIDMismatch is returned when an incorrect 'collectionUUID' field is provided on all commands.

The behavior of shardCollection() when called on a timeseries view namespace with a non-existent 'collectionUUID' field yields

"Taking <dbName.collName> lock for timeseries is not allowed"

Whereas the same set of operations returns CollectionUUIDMismatch on a non-timeseries view namespace.

Participants:: [DO NOT USE] Backlog - Storage Execution Team, Haley Connelly