[SERVER-42041] Enable db.setProfilingLevel on mongoS and push down to all members (P,S) of the sharded cluster Created: 02/Jul/19  Updated: 20/Sep/22  Resolved: 16/Jul/19

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

Type: Improvement Priority: Major - P3
Reporter: Shakir Sadikali Assignee: Eric Sedor
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-12521 Can't use system.profile on a sharded... Closed
Participants:
Case:

 Description   

SERVER-1957 skims some of what this request asks.

We are trying to troubleshoot an imbalance of load across shards and auto enabling/disabling of profiling on all members easily would be useful. We currently have to log into each member and individually enable/disable profiling. To process the data we need to mongodump and restore it individually to some other central location.

It would be good if this (and other supporting commands) could

  • run from a given mongos
  • push the command down to the mongod processes for every Shard Primary (and/or Secondary)
  • store the data in a single place or make it accessible from a single place (i.e. mongodump from a mongoS but it would collect it from each member for you)


 Comments   
Comment by Eric Sedor [ 03/Jul/19 ]

Hi shakir.sadikali, we recently decided against changes to current profiling mechanisms in SERVER-12521, but do appreciate your input that this is something that would be useful to you. That will help us prioritize similar improvements in the future.

Generated at Thu Feb 08 04:59:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.