[SERVER-26288] CSRS Continuous stepdown suite log verbosity causing failures on slow machines Created: 23/Sep/16  Updated: 19/Nov/16  Resolved: 07/Nov/16

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Misha Tyulenev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-11-21
Participants:
Linked BF Score: 0

 Description   

The log churn appears to be saturating the I/O in some of the low powered test machines



 Comments   
Comment by Githook User [ 07/Nov/16 ]

Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: SERVER-26288 reduce log verbosity for continuous stepdown suite
Branch: master
https://github.com/mongodb/mongo/commit/f9463844312aa7812c4072de18d5eeb29fa5b00c

Comment by Misha Tyulenev [ 04/Nov/16 ]

The original fix had a conflict when passing setParameter from ShardingTest.

Comment by Githook User [ 04/Nov/16 ]

Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: Revert "SERVER-26288 reduce log verbosity for continuous stepdown suite"

This reverts commit 0b47329d93f0d2ca7bab21775cb83e20dfe7c68f.
Branch: master
https://github.com/mongodb/mongo/commit/361efe3a8d6675b258b92a6f701a98123c4b613d

Comment by Githook User [ 03/Nov/16 ]

Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: SERVER-26288 reduce log verbosity for continuous stepdown suite
Branch: master
https://github.com/mongodb/mongo/commit/0b47329d93f0d2ca7bab21775cb83e20dfe7c68f

Comment by Andy Schwerin [ 27/Oct/16 ]

We should reduce the log level for mongos from 2 to 0 or 1, except for the components we actually want more logging out of.

Generated at Thu Feb 08 04:11:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.