Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Operating System:
ALL
Sprint:
Sharding EMEA 2022-05-02, Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30, Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11
Linked BF Score:
137
Confidence Status:
None
Work Order:
3

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

Currently, in stepUp while holding the RSTL, we recover the sharding state which includes making remote calls to the config server. This seems non-ideal and a liveness issue as we end up blocking while something has gone wrong with the config server.

depends on

SERVER-60110 Get rid of ShardingStateRecovery once 7.0 branches out

Closed

is related to

SERVER-38409 Shard can crash at step-up due to FailedToSatisfyReadPreference exception during minOpTime recovery

Closed

SERVER-56756 Primary cannot stepDown when experiencing disk failures

Closed

Assignee:: Jordi Serra Torrens
Reporter:: Jason Chan
Participants:: Jason Chan, Jordi Serra Torrens
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Apr 18 2022 09:40:50 PM UTC
Updated:: Jul 01 2022 01:24:06 PM UTC
Resolved:: Jul 01 2022 01:23:59 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates