41:34  INFO (io.tilt.minka.domain.WebServer.main()-EventThread) Leader: Registering as Leader at well after waiting 46269 msecs
41:34  INFO (io.tilt.minka.domain.WebServer.main()-EventThread) Leader: 46529 msec since load till leader election
41:34  INFO (io.tilt.minka.domain.WebServer.main()-EventThread) Proctor: Starting. Scheduling constant shepherding check
41:34  INFO (io.tilt.minka.domain.WebServer.main()-EventThread) Distributor: Starting. Scheduling constant periodic check
41:34  INFO (io.tilt.minka.domain.WebServer.main()-EventThread) FollowerEventsHandler: Starting. Scheduling constant shepherding check
41:34  INFO (io.tilt.minka.domain.WebServer.main()-EventThread) ClientEventsHandler: Starting
41:35  INFO (MKS-1) ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Analyzing Shards (i0) by Leader: 192.168.1.102:9000 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
41:35  WARN (MKS-1) Proctor: Partition queue empty: no shards emiting heartbeats ?
41:35  INFO (MKS-1) ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
41:38  INFO (MKS-7) Stage: Adding new Shard 192.168.1.102:9000
41:39  INFO (MKS-2) ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Analyzing Shards (i4) by Leader: 192.168.1.102:9000 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
41:39  INFO (MKS-2) Proctor: Health: STABLE, 1 shard(s) going to be analyzed: [192.168.1.102:9000]
41:39  INFO (MKS-2) Proctor: 192.168.1.102:9000 stays in JOINING, no enough heartbeats in lapse, (1/0), Seq [1..1] ❇
41:39  WARN (MKS-2) Proctor: Cluster back to: UNSTABLE (0, min unchanged analyses: 1)
41:39  INFO (MKS-2) ——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————