[SERVER-57870] Drop database sharded FSM doesn't guarantee that operations will be completed Created: 21/Jun/21  Updated: 29/Oct/23  Resolved: 08/Jul/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.1.0, 5.0.0-rc7
Fix Version/s: 5.0.2, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-07-12
Participants:
Linked BF Score: 41

 Description   

This FSM and its derivatives are continuously dropping and recreating the Database/collections, so it can totally happen that an operation ends up failing with a StaleDbVersion after a few retries.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 21/Jul/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-57870 Drop database sharded FSM must handle StaleDBVersion exceptions
Branch: v5.0
https://github.com/mongodb/mongo/commit/839f2e6dd09665a785b76426ff1517d0e3412048

Comment by Githook User [ 08/Jul/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-57870 Drop database sharded FSM must handle StaleDBVersion exceptions
Branch: master
https://github.com/mongodb/mongo/commit/88e49749c4898089daba99cf7cb26d3f2e9aa3f6

Generated at Thu Feb 08 05:43:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.