[SERVER-36972] SHARDING CatalogCacheLoader + Balancer filling up to several gb log in little time Created: 03/Sep/18  Updated: 25/Sep/18  Resolved: 25/Sep/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.6, 3.6.7
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gianluca Botta Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-30841 Lower the amount of metadata refresh ... Closed
Operating System: ALL
Participants:

 Description   

We have two different deployments.

Last week we upgraded them:

  • one from 3.4.16 to 3.6.6
  • other from 3.4.16 to 3.6.7

Now the mongod configuration config server keeps spamming us with these message non stop:

2018-09-03T10:11:20.922+0200 I SHARDING [Balancer] Refreshing chunks for collection (collection name) based on version 8|1||59de38102edb75dfb0677947
2018-09-03T10:11:20.923+0200 I SHARDING [ConfigServerCatalogCacheLoader-37073] Refresh for collection (collection name) took 0 ms and found version 8|1||59de38102edb75dfb0677947

 

this issue causes a huge log file in a very little time



 Comments   
Comment by Kelsey Schubert [ 25/Sep/18 ]

Thanks for the additional info, jamesbotta. I completed the backport for SERVER-30841, and it's included in MongoDB 3.6.8, which was released last week if you'd like to upgrade.

Comment by Gianluca Botta [ 07/Sep/18 ]

Hi Kelsey T Schubert,

currently, on config mongod,  the log file grows about 2 Gbs a day

Comment by Kelsey Schubert [ 07/Sep/18 ]

Hi jamesbotta,

Thanks for the report. SERVER-30841 describes a fix to reduce the amount of metadata refresh logging, and has been approved for backport to 3.6. I would recommend watching it for updates.

Would you please clarify the rate at which your logs are growing as a result of these messages? How much time elapses before it reaches a certain size?

Thanks,
Kelsey

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