Example of chatty logging:
2017-08-22T12:02:14.386+1000 I SHARDING [Balancer] Refreshing chunks for collection mytest.test1 based on version 0|0||000000000000000000000000 2017-08-22T12:02:14.387+1000 I SHARDING [CatalogCacheLoader-0] Refresh for collection mytest.test1 took 0 ms and found version 1|0||599b909d11c6b22dd4ad5548
These logs don't convey knowledge to our users and are not actionable. On the config server, they can spam to a user with many sharded collection in our auto-balancing code every 10 seconds because we force refresh for every chunk the balancer attempts to move.
The logs come from the CatalogCache and the CatalogCacheLoader.
The logs were useful while we were trying to stabilize the new/modified refresh logic, but less so now, and our testing can retain the same information with log-level 1 set.
- is duplicated by
-
SERVER-36180 Sharding: Config server log spamming every 10 seconds in 3.6.6
- Closed
-
SERVER-36972 SHARDING CatalogCacheLoader + Balancer filling up to several gb log in little time
- Closed
- is related to
-
SERVER-43021 MongoS server crashes when attempt to update single record > 16MB (16793648)
- Closed
-
SERVER-8245 logging cleanup: review severity of sharding log messages
- Closed