[SERVER-55616] Instances of ShardingDDLCoordinator are not throwing on NotPrimaryError nor ShutdownError - MongoDB Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 5.0.0-rc0
Component/s: Sharding
Labels:
- PM-1965-Milestone-1

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2021-04-05
Linked BF Score:
165

Description

The current implementation of the onCompletion callback on the instances of the ShardingDDLCoordinator are simply returning if there was a NotPrimaryError or ShutdownError category, if there is a write and the DDL operation fails because of a stepdown, then that error would not propagate to the router nor the operation retried, giving an ok:0 result to the user when actually the operation haven't finished. We should throw on those categories but leaving the current approach of not removing the coordinator document on those scenarios.

Attachments

Issue Links

is caused by

SERVER-54587 Make create collection resilient to stepdowns

Closed

SERVER-54605 Make rename collection coordinator resilient to stepdowns

Closed

SERVER-54944 Make drop collection resilient to stepdowns

Closed

SERVER-54945 Make drop database resilient to stepdowns on sharded cluster

Closed

Activity

People

Assignee:: Marcos José Grillo Ramirez

Reporter:: Marcos José Grillo Ramirez

Participants:: Githook User, Marcos José Grillo Ramirez

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: Mar 30 2021 10:45:32 AM UTC

Updated:: May 25 2021 10:09:09 PM UTC

Resolved:: Mar 31 2021 12:53:02 PM UTC