Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.0-rc0
Affects Version/s: 3.7.1
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2018-04-09, Sharding 2018-04-23, Sharding 2018-05-07, Sharding 2018-05-21
Linked BF Score:
20
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

For example, in removeShard command it get trigger a ShardRegistry refresh, but it uses the same operation context to do a readConcern majority read, and this can cause some weird behavior because the command will think that shards exists, when in fact they no longer do.

is duplicated by

SERVER-31414 The writes of _configsvrEnableSharding to config.databases do not use local write concern

Closed

SERVER-33256 shardCollection gets DuplicateKeyError if it retries inserting to config.collections after failing to wait for writeConcern

Closed

is related to

SERVER-30559 Sharding tests which run under continuous stepdown must allow for lastVisibleOp to go backwards

Closed

related to

SERVER-37929 ShardRegistry in config servers can keep invalid entries after it rolls back until next reload

Closed

Assignee:: Blake Oler
Reporter:: Randolph Tan
Participants:: Blake Oler, Githook User, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Dec 15 2017 10:50:49 PM UTC
Updated:: Oct 30 2023 11:09:51 PM UTC
Resolved:: May 10 2018 07:32:41 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates