[SERVER-36180] Sharding: Config server log spamming every 10 seconds in 3.6.6 Created: 18/Jul/18  Updated: 06/Dec/22  Resolved: 18/Jul/18

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

Type: Bug Priority: Major - P3
Reporter: Vick Mena (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
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
Assigned Teams:
Sharding
Operating System: ALL
Steps To Reproduce:
  1. mlaunch init --replicaset --nodes 1 --shards 1 --configs 1 --verbose --hostname localhost --bind_ip localhost --wiredTigerCacheSizeGB 0.1
  2. mongo --eval "sh.enableSharding('test'); sh.shardCollection('test.c', {_id:1})"
  3. tail -f data/configRepl/rs1/mongod.log
Participants:
Case:

 Description   

3.6.6-ent is logging the following every 10 seconds for a freshly sharded empty collection

2018-07-18T11:20:02.052-0400 I SHARDING [Balancer] Refreshing chunks for collection test.c based on version 1|0||5b4f59b1ebe2a7c29b1d48b9
2018-07-18T11:20:02.053-0400 I SHARDING [ConfigServerCatalogCacheLoader-0] Refresh for collection test.c took 0 ms and found version 1|0||5b4f59b1ebe2a7c29b1d48b9

Similar to SERVER-29149 which is closed. This appears to be coming from the catalog cache

s/catalog_cache.cpp
441:    log() << "Refreshing chunks for collection " << nss << " based on version "



 Comments   
Comment by Kaloian Manassiev [ 18/Jul/18 ]

We are doing to address the verbosity of the sharding metadata refresh logging under SERVER-30841. This is not new to 3.6, right? This particular logging has been there since 3.4.

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