[SERVER-21168] Dropping database does not clear state of contained collections in Top Created: 27/Oct/15  Updated: 02/Sep/16  Resolved: 19/Aug/16

Status: Closed
Project: Core Server
Component/s: Admin, Storage
Affects Version/s: None
Fix Version/s: 3.3.12

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: Kyle Suarez
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-6627 top command should return cursor Backlog
is related to SERVER-21167 Top keeps state about operations agai... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Integration 18 (08/05/16), Integration 2016-08-29
Participants:

 Description   

Dropping a database fails to clear the state in Top associated with the contained collections. This is unexpected.

See also related ticket SERVER-21167.

Reproduce with the following script:

db.dropDatabase();
db.foo.insert({});
db.dropDatabase();
assert.isnull(db.adminCommand("top").totals["test.foo"]);  // Trips: unexpected.



 Comments   
Comment by Githook User [ 19/Aug/16 ]

Author:

{u'username': u'kevinAlbs', u'name': u'Kevin Albertson', u'email': u'kevin.albertson@10gen.com'}

Message: SERVER-21168 Update top on database drop
Branch: master
https://github.com/mongodb/mongo/commit/9efbffec2c4be8c597a6d39ba3474f5d4a110454

Comment by Kyle Suarez [ 19/Aug/16 ]

Throwing this back on the Integration Team backlog as kevin.albertson's internship is coming to a close.

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