[SERVER-22070] log of config replica is too verbose Created: 06/Jan/16  Updated: 13/Jan/16  Resolved: 12/Jan/16

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

Type: Bug Priority: Major - P3
Reporter: Hoyt Ren Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File config01.log    
Operating System: ALL
Participants:

 Description   

I setup a v3.2 replica set with 3 members, and let it work as a config server of my mongos. When I check the log, I see a lot of "update" commands while these operations look successful within 1 second. I believe they should not be there, because I already set all log verbosity to 0, and "operationProfiling.mode" to "off", in my config file. My normal replicas seems don't have this problem.



 Comments   
Comment by Hoyt Ren [ 13/Jan/16 ]

Hi Thomas,

Thank you very much for your patience. I'm clear now. This is due to my configuration. I will think about is it necessary to be twisted.

Comment by Kelsey Schubert [ 12/Jan/16 ]

Hi Hoyt Ren,

I wanted to clarify that this is the expected behavior on any replica set regardless of whether it is set up as a config replica set:

As Dan mentioned, slowOpThresholdMillis can be modified. However, it is not necessary in this case.

If you have additional questions on profiling and logging please post on the mongodb-users group.

Thank you,
Thomas

Comment by Hoyt Ren [ 12/Jan/16 ]

Hi Dan,

Yes,each host has multiple mongod. Maybe we will separate them later.

Do you mean when the rs is config rs. The "operationProfiling.mode" will be ignored and the "operationProfiling.slowOpThresholdMs" always be 100ms as designed? I'm ok with it, just want to confirm. As you said, it's usually fast. It's slow because I was importing data, then no problem, thanks。

Comment by Daniel Pasette (Inactive) [ 12/Jan/16 ]

Hi Hoyt,
Those log messages are normal, but they are important to log because they indicate that an operation took longer than expected. They are logged because they took > 100ms. See the documentation on the slowOpThresholdMillis. I would recommend against changing this setting.

Are you running any other applications or mongodb instances on the same hosts as your config server? In general, those operations should be quite fast on your config server replica set.

Comment by Hoyt Ren [ 07/Jan/16 ]

Attached file config01.log.

When it happens, I was importing a lot of data with mongoimport to mongos.

Comment by Daniel Pasette (Inactive) [ 06/Jan/16 ]

Can you attach the log file from your server to this ticket?

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