[SERVER-2423] command line option --quiet does not silence config server output Created: 27/Jan/11  Updated: 06/Apr/23  Resolved: 25/Jan/18

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

Type: Improvement Priority: Minor - P4
Reporter: Nathan D Acuff Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux (multiple)


Assigned Teams:
Sharding
Participants:

 Description   

Despite specifying --quiet, our config servers still add this to their logs continuously:

Thu Jan 27 19:31:20 [conn2] fsync from getlasterror
Thu Jan 27 19:31:30 [conn1] CMD fsync: sync:1 lock:0
Thu Jan 27 19:31:30 [conn1] fsync from getlasterror
Thu Jan 27 19:31:30 [conn2] CMD fsync: sync:1 lock:0
Thu Jan 27 19:31:30 [conn2] fsync from getlasterror
Thu Jan 27 19:31:36 [conn1] CMD fsync: sync:1 lock:0
Thu Jan 27 19:31:36 [conn1] fsync from getlasterror
Thu Jan 27 19:31:36 [conn1] CMD fsync: sync:1 lock:0



 Comments   
Comment by Scott Lowe [ 09/Jul/13 ]

I think this is supposed to have been addressed in SERVER-5442? (Although that fix is not working for me)

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