[SERVER-16638] remove fsync messages from config server logs Created: 22/Dec/14  Updated: 06/Dec/22  Resolved: 02/Nov/15

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

Type: Improvement Priority: Minor - P4
Reporter: joe piscitella Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-17151 Avoid fsync command in ConfigCoordinator Closed
Related
is related to SERVER-17300 Balancer tries to create config.tags ... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Sprint: Sharding C (11/20/15)
Participants:

 Description   

running 3 shard cluster with 3 config servers. after the mongo 2.6 upgrade noticed the amount of logging into mongoc logs-

jira shows the --quiet flag could be used to supress the messages from the log but it doesnt seem to be working. https://jira.mongodb.org/browse/SERVER-5442

2014-12-22T14:02:05.681-0700 [initandlisten] MongoDB starting : pid=2060 port=27019 dbpath=/db/configdb master=1 64-bit host=X
2014-12-22T14:02:05.682-0700 [initandlisten] db version v2.6.5
2014-12-22T14:02:05.682-0700 [initandlisten] git version: e99d4fcb4279c0279796f237aa92fe3b64560bf6
2014-12-22T14:02:05.682-0700 [initandlisten] build info: Linux build8.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2014-12-22T14:02:05.682-0700 [initandlisten] allocator: tcmalloc
2014-12-22T14:02:05.682-0700 [initandlisten] options: { sharding: { clusterRole: "configsvr" }, storage: { dbPath: "/db/configdb" }, systemLog: { destination: "file", path: "/var/log/mongodb/mongoc.log", quiet: true } }
2014-12-22T14:02:05.683-0700 [initandlisten] journal dir=/db/configdb/journal
2014-12-22T14:02:05.683-0700 [initandlisten] recover : no journal files present, no recovery needed
2014-12-22T14:02:05.716-0700 [initandlisten] waiting for connections on port 27019
2014-12-22T14:02:06.212-0700 [conn2] first cluster operation detected, adding sharding hook to enable versioning and authentication to remote servers
2014-12-22T14:02:08.125-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.129-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.132-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.148-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.158-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.161-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.164-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.166-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.169-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.171-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.176-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.180-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.183-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.185-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.188-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.191-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.193-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.195-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.197-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.199-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.201-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.204-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.206-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.208-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.210-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.212-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.214-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.216-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.218-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.220-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.222-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.224-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.226-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.229-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.231-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.234-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.236-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.240-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.242-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.244-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.246-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.248-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.250-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.252-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.254-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.258-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.260-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.263-0700 [conn16] CMD fsync: sync:1 lock:0
2014-12-22T14:02:08.266-0700 [conn16] CMD fsync: sync:1 lock:0



 Comments   
Comment by Andy Schwerin [ 27/Oct/15 ]

This issue may now be resolved. We'll recheck on the master branch.

Comment by Ramon Fernandez Marina [ 15/Jan/15 ]

jpiscitella, I'm re-purposing this ticket as an enhancement request to remove the fsync messages altogether, as they don't seem to serve much of a purpose these days.

Comment by Ramon Fernandez Marina [ 08/Jan/15 ]

jpiscitella, these messages are a known issue, and we're discussing how to improve the situation.

The amount of fsync messages should not cause any issues in term of log size and only add noise. If you want to get rid of these messages, off the top of my head a possible workaround (if you're running on Linux) would be to log to syslog and filter them out (e.g.: with rsyslog).

Comment by Ramon Fernandez Marina [ 07/Jan/15 ]

Hi jpiscitella, thanks for your report. I do see the "CMD fsync:" messages and I'm investigating whether there's something that can be done about them.

Looking at SERVER-5442, the code changes didn't suppress these 'fsync' messages in the config server logs when '--quiet' is supplied on the command line, but rather it changes the behavior such that the system uses 'journal commit' rather than the 'fsync' command for config server writes. This change effectively reduces the frequency these messages will be seen in the config server logs.

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