No bloom filters from AP1, US1 and EU1

[littleskunk]

@CubeFan

I use a script from a friend that reads out the status of the filewalker, so I can see which one has been running since the nodestart or since when it is finished.

Nice one. I like that. Just be aware that the used space numbers you see there will be off the longer the used space filewalker takes. The corresponding fix will be included in v1.109.

74e3afe storagenode/pieces: run cache persistence loop concurrently with the used space calculation

@CubeFan

if you tell me exactly how I have to do this, I will be happy to do so. I currently have one GC running but 3 trash filewalkers and 1 used space with 10 nodes

Guide to debug my storage node, uplink, s3 gateway, satellite

We have integrated a package called monkit in all storage nodes. It is very usefull for debuging. By default it will open a random port. In order to connect to the debug port you will need to: Add debug.addr: ":5999" to the config file. Now the port is fixed and will not change on every restart. Add -p 127.0.0.1:5999:5999 to the docker run command. Ready for action! You can request the following informations: curl localhost:5999/mon/funcs Find out how long a function like GetExpired need…

@CubeFan

the nodes have been online for about 10 days without interruption, filters from saltlake arrive at all nodes. Today, however, some of EU1 arrived, which is great So unfortunately that’s not the problem in this case either.

I would like to add one to the list:
5. bloom filter sender crashed. That would also give some nodes a bloom filter to work with while others don’t get one. More likely to happen on SLC and US1 because they are bigger. I would be surprised to see it on AP1.

Usually the bloom filter arrive over the weekend so between Friday and Sunday. So EU1 might be a bit early this week.