[SERVER-55033] OpObserverImpl should pass the shard key when calling shardObserveDeleteOp Created: 08/Mar/21  Updated: 29/Oct/23  Resolved: 10/Mar/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.9.0-alpha4
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-47531 OpObserver: Convert usage of getColle... Closed
Related
is related to SERVER-55111 When using a nested shard key, a dele... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-03-22
Participants:
Linked BF Score: 121

 Description   

OpObserverImpl is only passing the document '_id' when calling shardObserveDeleteOp. However, it should also mass the shardKey element, because OpObserverShardingImpl::shardObserveDeleteOp needs it so that in assertIntersectingChunkHasNotMoved it is able to find the intersecting chunk.

This line should be changed to:

documentKey.getShardKeyAndId(),



 Comments   
Comment by Githook User [ 10/Mar/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-55033: OpObserverImpl should pass the shard key when calling shardObserveDeleteOp
Branch: master
https://github.com/mongodb/mongo/commit/e65a165eeff3b74460e94b76fbf9dca5a2f40b75

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