[SERVER-49147] Make _configsvrCommitChunkMigration idempotent Created: 26/Jun/20  Updated: 29/Oct/23  Resolved: 29/Jul/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.5.1
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-1, sharding-csrs-stepdown-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes SERVER-50215 _configsvrCommitChunkMigration might ... Closed
causes SERVER-50458 Re-enable retryability of commitChunk... Closed
causes SERVER-50577 Return actual donor shard version in ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10
Participants:
Linked BF Score: 40

 Description   

Right now, if _configsvrCommitChunkMigration is run twice upon the config server, the second call results in an error even if the migration actually succeeded.

Possible fixes:

  • On the config server, checking both donor and recipient in checkChunkMatchesRequest
  • On the shard, double check that the chunk is still owned before a call to _configsvrCommitChunkMigration (it doesn't make the command idempotent, but it guarantees that it doesn't get called more than once)


 Comments   
Comment by Githook User [ 30/Jul/20 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-49147 fix mac os x compile
Branch: master
https://github.com/mongodb/mongo/commit/645a1b57976bbebc3c2a16dfc7a178ca3791d2d9

Comment by Githook User [ 29/Jul/20 ]

Author:

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

Message: SERVER-49147 Make _configsvrCommitChunkMigration idempotent
Branch: master
https://github.com/mongodb/mongo/commit/bb8d69f859c2db05520469f57428198c8f451b90

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