-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Labels:None
-
ALL
I have 3.4.16 shard setup.
The shard balancer is disabled with sh.getBalancerState(false);
However sometimes the shard balancer kicks in. This is traces from primary of the config server.
2018-07-25T05:47:46.378+0000 I SHARDING [CatalogCacheLoader-4] Refresh for collection tss-perf.invalid_session_data took 0 ms and found version 8|17||5b578740f2d767f3033daa75
2018-07-25T05:47:46.378+0000 I SHARDING [Balancer] Refreshing chunks for collection tss-perf.status_messages based on version 8|17||5b578732f2d767f3033da9db
2018-07-25T05:47:46.378+0000 I SHARDING [CatalogCacheLoader-5] Refresh for collection tss-perf.status_messages took 0 ms and found version 8|17||5b578732f2d767f3033da9db
2018-07-25T05:47:46.379+0000 I SHARDING [Balancer] Refreshing chunks for collection tss-perf.event_logs based on version 9|1||5b57871cf2d767f3033da8d2
2018-07-25T05:47:46.379+0000 I SHARDING [CatalogCacheLoader-4] Refresh for collection tss-perf.event_logs took 0 ms and found version 9|1||5b57871cf2d767f3033da8d2
2018-07-25T05:47:46.382+0000 I SHARDING [Balancer] Refreshing chunks for collection tss-perf.test_responses based on version 13|1||5b5786f8f2d767f3033da771
2018-07-25T05:47:46.382+0000 I SHARDING [CatalogCacheLoader-5] Refresh for collection tss-perf.test_responses took 0 ms and found version 13|1||5b5786f8f2d767f3033da771
2018-07-25T05:47:46.385+0000 I SHARDING [Balancer] distributed lock 'tss-perf.test_responses' acquired for 'Migrating chunk(s) in collection tss-perf.test_responses', ts : 5b563239f8c6413de2362af0
2018-07-25T05:47:46.388+0000 I SHARDING [Balancer] Refreshing chunks for collection tss-perf.test_session_states based on version 12|1||5b578710f2d767f3033da85a
2018-07-25T05:47:46.388+0000 I SHARDING [CatalogCacheLoader-4] Refresh for collection tss-perf.test_session_states took 0 ms and found version 12|1||5b578710f2d767f3033da85a
2018-07-25T05:47:46.391+0000 I SHARDING [Balancer] distributed lock 'tss-perf.test_session_states' acquired for 'Migrating chunk(s) in collection tss-perf.test_session_states', ts : 5b563239f8c6413de2
362af0
2018-07-25T05:47:46.394+0000 I SHARDING [Balancer] Refreshing chunks for collection tss-perf.test_session_states based on version 12|1||5b578710f2d767f3033da85a
2018-07-25T05:47:46.394+0000 I SHARDING [CatalogCacheLoader-5] Refresh for collection tss-perf.test_session_states took 0 ms and found version 12|1||5b578710f2d767f3033da85a
2018-07-25T05:47:46.397+0000 I SHARDING [Balancer] Refreshing chunks for collection tss-perf.event_logs based on version 9|1||5b57871cf2d767f3033da8d2
2018-07-25T05:47:46.398+0000 I SHARDING [CatalogCacheLoader-4] Refresh for collection tss-perf.event_logs took 0 ms and found version 9|1||5b57871cf2d767f3033da8d2
2018-07-25T05:47:46.401+0000 I SHARDING [Balancer] distributed lock 'tss-perf.event_logs' acquired for 'Migrating chunk(s) in collection tss-perf.event_logs', ts : 5b563239f8c6413de2362af0
2018-07-25T05:47:46.425+0000 I SHARDING [NetworkInterfaceASIO-ShardRegistry-0] distributed lock with ts: '5b563239f8c6413de2362af0' and _id: 'tss-perf.test_responses' unlocked.
2018-07-25T05:47:46.456+0000 I SHARDING [NetworkInterfaceASIO-ShardRegistry-0] distributed lock with ts: '5b563239f8c6413de2362af0' and _id: 'tss-perf.test_session_states' unlocked.
2018-07-25T05:47:46.493+0000 I SHARDING [NetworkInterfaceASIO-ShardRegistry-0] distributed lock with ts: '5b563239f8c6413de2362af0' and _id: 'tss-perf.event_logs' unlocked.
2018-07-25T05:47:46.496+0000 I SHARDING [Balancer] about to log metadata event into actionlog: { _id: "ip-172-31-72-228.ec2.internal-2018-07-25T05:47:46.496+0000-5b580f02f8c6413de26c43ed", server: "ip
-172-31-72-228.ec2.internal", clientAddr: "", time: new Date(1532497666496), what: "balancer.round", ns: "", details: { executionTimeMillis: 180, errorOccured: false, candidateChunks: 4, chunksMoved:
4 } }