[SERVER-12521] Can't use system.profile on a sharded cluster Created: 29/Jan/14  Updated: 03/Jul/19  Resolved: 29/Jan/14

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

Type: Bug Priority: Major - P3
Reporter: Avishay Lavie Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-1957 implement profile for mongos Closed
is duplicated by SERVER-42041 Enable db.setProfilingLevel on mongoS... Closed
Operating System: ALL
Participants:

 Description   

It is unclear from the documentation how to use the query profiler in a sharded cluster, and the results are confusing.

I can't use setProfilingLevel on a mongos server, so I have to set it individually on each shard. This leads to a 'system.profile' collection appearing when connecting to the mongos, but it claims to contain only 92 documents whereas each shard contains much more than that.

I expected the system.profile collection on the mongos to act like any other sharded collection, and represent the combined contents of the system.profile collection on each shard. This is not happening, so either it's a bug, or the usage/docs are misleading.

In short, I'm missing a reliable and clearly-documented way to get system.profile data from the entire cluster.



 Comments   
Comment by Scott Hernandez (Inactive) [ 29/Jan/14 ]

Yes, there is a plan to do this in the future: SERVER-1957

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