Operational Defect Database

BugZero found this defect 2401 days ago.

MongoDB | 410791

[SERVER-30450] in shardCollection, get UUID from shard only after validating or creating indexes, to ensure collection exists on shard

Last update date:

8/1/2017

Affected products:

MongoDB Server

Affected releases:

3.5.10

Fixed releases:

No fixed releases provided.

Description:

Info

This means we'll have to call listCollections twice on the primary shard if we want to avoid shardCollection being able to fail after creating the collection on the shard. We should avoid this because the user may change the options to shardCollection to try to fix their issue, and the new options may be incompatible with the options the collection was just created with. For example, if the first (failed) shardCollection attempt specified one shard key and passed the 'unique' option, and the second attempt specifies a different shard key, the second attempt will fail because a unique index was created on the shard with the first key. Depends on SERVER-29858, since we don't want to add new uses of DBClient in sharding, but ShardRemote does not have a way to iterate a cursor on shards.

Top User Comments

esha.maharishi@10gen.com commented on Tue, 1 Aug 2017 14:56:12 +0000: Will be done as part of SERVER-29760.

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...