[SERVER-69586] Make update/delete of range deletion document on recipient idempotent Created: 12/Sep/22  Updated: 29/Oct/23  Resolved: 19/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-09-19
Participants:

 Description   

jordi.serra-torrens@mongodb.com pointed out that there may be a very improbable but still relevant bug after the changes committed under SERVER-69555.

The migration coordinator is asking the recipient to unset the pending field (in case of commit) or delete the range deletion document (in case of abort).

Since targeting is not done anymore by migrationId, it may happen the following:

  • An update/delete on the recipient succeeds, but the request gets stuck in the network and is also retried after 1 hour.
  • After 1 hour, a new migration involving the same range may be happening, and the update/deletion would be wrongly applied.


 Comments   
Comment by Githook User [ 16/Sep/22 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-69586 Make update/delete of range deletion document on recipient idempotent
Branch: master
https://github.com/mongodb/mongo/commit/cae95e44291d09e1515bf85860d0ffe1632ce572

Generated at Thu Feb 08 06:13:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.