Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36180

Sharding: Config server log spamming every 10 seconds in 3.6.6

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.6
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • Hide
      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
      Show
      mlaunch init --replicaset --nodes 1 --shards 1 --configs 1 --verbose --hostname localhost --bind_ip localhost --wiredTigerCacheSizeGB 0.1 mongo --eval "sh.enableSharding('test'); sh.shardCollection('test.c', {_id:1})" tail -f data/configRepl/rs1/mongod.log
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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 "

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            vick.mena Vick Mena (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: