-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.4
-
Component/s: Sharding
-
None
-
ALL
-
We have deployed a new production set-up using the same configuration that we have for the other one, however for this one the mongod configuration server keeps spamming us with these message non stop:
2017-05-11T17:12:18.303+0000 I SHARDING [Balancer] Refreshing chunks for collection (collection) based on version 1|0||590245312abfdf91c6d415fe
2017-05-11T17:12:18.303+0000 I SHARDING [CatalogCacheLoader-25] Refresh for collection (Collection) took 0 ms and found version 1|0||590245312abfdf91c6d415fe
This lead us to having to rotate and delete all log after a 1 hour period. it is started in quiet mode with verbosity set to 0. The chunk size have been modified to 128mb and it's been like that since we've set-up the server and I can't figure out why it's happening only on this 3 machine clusters
Thanks !
Stéphane
- duplicates
-
SERVER-28418 make the split command on mongod return a stale version error if the requested chunk bounds are not found
- Closed