[SERVER-60413] Fix the critical section reason used by the moveChunk command Created: 04/Oct/21  Updated: 29/Oct/23  Resolved: 13/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0, 5.0.4, 5.1.0-rc1

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.1, v5.0
Sprint: Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
Participants:

 Description   

The reason computed here is using an object that was already moved.



 Comments   
Comment by Githook User [ 13/Oct/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-60413 Fix the critical section reason used by moveChunk

(cherry picked from commit 628aa5d9fe2624d40bb1b0a041521806e7d03d86)
Branch: v5.1
https://github.com/mongodb/mongo/commit/373880c8a396f9b71988654503beb8cbd5e39f31

Comment by Githook User [ 13/Oct/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-60413 Fix the critical section reason used by moveChunk

(cherry picked from commit 628aa5d9fe2624d40bb1b0a041521806e7d03d86)
Branch: v5.0
https://github.com/mongodb/mongo/commit/94a46e3f45191b4a4bb41e502384b91f948df243

Comment by Githook User [ 13/Oct/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-60413 Fix the critical section reason used by moveChunk
Branch: master
https://github.com/mongodb/mongo/commit/628aa5d9fe2624d40bb1b0a041521806e7d03d86

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