[SERVER-10099] Get profiling status via the REST interface create a database if it does not exist Created: 04/Jul/13  Updated: 10/Dec/14  Resolved: 13/Aug/13

Status: Closed
Project: Core Server
Component/s: HTTP Console
Affects Version/s: 2.4.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: David Regnier Assignee: Stennie Steneker (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-2329 Dropped database doesn't disappear du... Closed
Operating System: ALL
Participants:

 Description   

Get profiling status using the REST interface create a database if it does not exist.

example: http://localhost:28017/test/$cmd/?filter_profile=-1&limit=1

creates the 'test' database if it does not exist.



 Comments   
Comment by Stennie Steneker (Inactive) [ 13/Aug/13 ]

Hi David,

Thank you for confirming. I'm going to resolve this as a duplicate of SERVER-2329; please watch/upvote that issue for updates.

Thanks,
Stephen

Comment by David Regnier [ 13/Aug/13 ]

Yes this is correct -> the database is empty and does not exist anymore when restarting mongod.

Thank you.

Comment by Stennie Steneker (Inactive) [ 13/Aug/13 ]

Hi David,

I believe this is a dupe of the same underlying issue as SERVER-2329/SERVER-7879.

If you run show dbs from the mongo shell you will likely see the non-existent database name you requested from the REST API listed, but the size will be (empty) (i.e. no data files have been preallocated). The database name will not persist after restarting mongod.

Can you confirm this via show dbs?

If the database is created at a non-zero size, can you provide the output of db.adminCommand('getCmdLineOpts')?

Thanks,
Stephen

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