[SERVER-14119] You should be able to set profiler from mongos Created: 31/May/14  Updated: 10/Dec/14  Resolved: 05/Jun/14

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

Type: Improvement Priority: Minor - P4
Reporter: David Murphy 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
Participants:

 Description   

Currently we can only set the profiling level via mongod's directly. The mongos layer is aware of primary and should accept

sh.setProfilingLevel(database,level, slowms) which in turn would then set it on each primary.



 Comments   
Comment by Thomas Rueckstiess [ 05/Jun/14 ]

Hi David,

I understand the linked ticket has been around for a while but we try to de-duplicate the SERVER project as much as possible to not lose track of issues.

We monitor pull requests separately, so if you submit your pull request against SERVER-1957, we will treat it in the same timeframe as we would for a new ticket.

Regards,
Thomas

Comment by David Murphy [ 05/Jun/14 ]

Thomas

I am not sure I am very happy with that given its was 2011 the last time a comment occurred and its in a planing bucket meaning its not being worked on really.
I opened this to track with a branch/pull request I am currently working on that is not in a stale ticket in JIRA

David

Comment by Thomas Rueckstiess [ 05/Jun/14 ]

Hi David,

thanks for opening this issue. As SERVER-1957 fully contains your request (Option A, and in addition has a second option B where mongos has its own in-memory profile), I'm closing this as a duplicate. Please watch SERVER-1957 and comment there for additional input if you like.

Regards,
Thomas

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