Konstantin Lebedev

@kaaaq The problem seems to be that before the collection was created, the master server lost the maxVolumeId values and created the collection with the already existing volume id. This...

> > This happens when all the master servers were turned off, and then turned on without the resumeState true option > > I am not sure whether the "resumeState"...

> Right. We can remove the "resumeState" option and always try to resume. It can also exclude the launch of the grow function until a collection with maxvolume appears in...

@chrislusf It seems like a raft server on the master, in addition to volumemaxid, stores the topology, but for some reason, when the leader changes, the topology is not saved....

I think fix.replication will start after and random delete Volume 1 from Servers 8080-8082. When deleting a volume, it can look at modified_at_second and size ?

Hello, yes, encrypting traffic on volumes seems redundant, so there are few such configurations. This is due to the fact that in several places the URL line contains a static...

I just launched volume in tls mode, no problems with that.

Add logging ``` > volume.check.disk -v -force volume 17, on 192.168.245.255:8081 and 192.168.245.255:8080. fileCount A: 277 != fileCount B: 276 load collection test volume 17 index size 4592 from 192.168.245.255:8081...

volume list with file_count:335 and file_count:331 ``` > volume.list -volumeId 19 Topology volumeSizeLimit:1024 MB hdd(volume:27/98 active:27 free:71 remote:0) DataCenter DefaultDataCenter hdd(volume:27/98 active:27 free:71 remote:0) Rack DefaultRack hdd(volume:27/98 active:27 free:71 remote:0)...

I also noticed something strange in counting the number of funks/files in the file volume I copy one volume id 5325 on local dev ``` Topology volumeSizeLimit:1024 MB hdd(volume:2/92 active:2...