[SERVER-1406] A drop database should be logged in the ConfigDB's changelog Created: 12/Jul/10  Updated: 12/Jul/16  Resolved: 13/Jul/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 1.5.5

Type: Improvement Priority: Minor - P4
Reporter: Alberto Lerner Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

A delete database can occur in between other events that are logged in sharded environment (splits, moves). Yet by looking at the configDB's changelog, one may not be aware of it. Logging drop database helps.



 Comments   
Comment by auto [ 13/Jul/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: log start/finish for drop database/collection SERVER-1406
http://github.com/mongodb/mongo/commit/fb4b8a3ec71f98ec03dd87336355bbc72cc3f202

Comment by Eliot Horowitz (Inactive) [ 13/Jul/10 ]

logged start/finish for drop database/collection

Generated at Thu Feb 08 02:56:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.