[SERVER-5442] use journal commit instead of fsync command for config server writes Created: 29/Mar/12  Updated: 06/Apr/23  Resolved: 05/Jun/13

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

Type: New Feature Priority: Minor - P4
Reporter: Stephen Young Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 3
Labels: configserver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-7850 Config server floods log with: CMD fs... Closed
Related
Participants:

 Description   

Allow --quiet flag on config servers to suppress fsync logging



 Comments   
Comment by Oleg Rekutin [ 05/Sep/13 ]

I take it back, I am seeing these fsyncs early on, but then die off and I don't see the same repeated volume. Hurray!

Comment by Oleg Rekutin [ 05/Sep/13 ]

Still seeing this on 2.4.6:

Thu Sep  5 22:38:51.018 [initandlisten] MongoDB starting : pid=8235 port=27017 dbpath=/media/ebs0/application-data/mongodb master=1 64-bit host=t3n1
Thu Sep  5 22:38:51.018 [initandlisten] db version v2.4.6
Thu Sep  5 22:38:51.018 [initandlisten] git version: b9925db5eac369d77a3a5f5d98a145eaaacd9673
Thu Sep  5 22:38:51.018 [initandlisten] build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49
Thu Sep  5 22:38:51.018 [initandlisten] allocator: tcmalloc
Thu Sep  5 22:38:51.018 [initandlisten] options: { configsvr: true, dbpath: "/media/ebs0/application-data/mongodb", fork: true, logpath: "/media/ebs0/application-logs/mongodb/configserver.log", port: 27017, quiet: true, rest: true }
Thu Sep  5 22:38:51.027 [initandlisten] journal dir=/media/ebs0/application-data/mongodb/journal
Thu Sep  5 22:38:51.027 [initandlisten] recover : no journal files present, no recovery needed
Thu Sep  5 22:38:51.198 [websvr] admin web console waiting for connections on port 28017
Thu Sep  5 22:38:51.198 [initandlisten] waiting for connections on port 27017
Thu Sep  5 22:38:52.677 [conn2] CMD fsync: sync:1 lock:0
Thu Sep  5 22:38:52.781 [conn2] CMD fsync: sync:1 lock:0
Thu Sep  5 22:38:52.896 [conn2] CMD fsync: sync:1 lock:0
Thu Sep  5 22:38:54.429 [conn6] CMD fsync: sync:1 lock:0
Thu Sep  5 22:38:54.492 [conn6] CMD fsync: sync:1 lock:0

Comment by Daniel Pasette (Inactive) [ 10/Jul/13 ]

are all servers in your cluster running 2.4.5? can you post a log file?

Comment by Scott Lowe [ 09/Jul/13 ]

I'm running 2.4.5 - the fsync entries are still being written to the logs.

Comment by Daniel Pasette (Inactive) [ 09/Jul/13 ]

this is only in 2.4.5

Comment by Scott Lowe [ 08/Jul/13 ]

I've added quiet=true to the mongodb.conf for the config servers, but am still getting these fsync entries in the logs. Does this fix not support the config file entry?

Comment by auto [ 19/Jun/13 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5442: need to resetError before doing the prepare
Branch: v2.4
https://github.com/mongodb/mongo/commit/f91d6f0a74e4410b93d6b30e2352fe589f71a5d7

Comment by auto [ 19/Jun/13 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5442: use journal commit instead of fsync command for config server writes
Branch: v2.4
https://github.com/mongodb/mongo/commit/310645dc7ba40a0ff3a48a7d3660d01e3e6d5da7

Comment by auto [ 06/Jun/13 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5442: need to resetError before doing the prepare
Branch: master
https://github.com/mongodb/mongo/commit/e93d63c4468b5dd65c4f3673544f25ac21bc7b52

Comment by auto [ 05/Jun/13 ]

Author:

{u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5442: use journal commit instead of fsync command for config server writes
Branch: master
https://github.com/mongodb/mongo/commit/cee9135e0f478bc60cbe599a6822c11fcbdb9dd0

Comment by Eliot Horowitz (Inactive) [ 05/Jun/13 ]

this addresses both performance and logging isues

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