[SERVER-55388] Bring back ShardingLogging calls to the drop collection Created: 22/Mar/21  Updated: 29/Oct/23  Resolved: 30/Mar/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: Backlog
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-52809 Implement the new drop collection pat... Closed
Related
is related to SERVER-55389 Bring back ShardingLogging calls to t... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-04-05
Participants:

 Description   

The new drop collection procedure introduced in SERVER-52809 doesn't log anymore in `config.changelog` through the ShardingLogging interface.

The goal of this ticket is to reintroduce the following two calls in the new drop collection coordinator:



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

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-55388 Bring back ShardingLogging calls to the drop collection
Branch: master
https://github.com/mongodb/mongo/commit/2737e53b543da043ae617fd1497ed8e85520508d

Comment by Antonio Fuschetto [ 30/Mar/21 ]

Code review URL: https://mongodbcr.appspot.com/760780002/

Comment by Tommaso Tocci [ 26/Mar/21 ]

antonio.fuschetto Since you already did SERVER-55389 I'll assign also this to you.

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