Node in eu, no traffic from eu satellite... why?

[Alexey]

@brainstorm

Surely you mean version 1.104.5 is latest, not 1.105.5

@ACarneiro

105.5 is currently rolling out

You are both correct that I provided a wrong version, and accordingly https://version.storj.io/ the default is 1.104.5 and 1.105.4 is in the rollout.

@brainstorm

I get constant 150Mb/s downloaded to my node by us and saltlake satellites

We uses wording from the customers’ point of view, so “downloads” = downloads from the Storj network = egress from the storage nodes. “Uploads” = uploads to the Storj network = ingress to the storage nodes.

So you actually said, that you have ingress from the customers of US1 and SLC satellites, and little ingress from the customers of the EU1 satellite.
This is quite possible, especially if your node is far away from these customers. We implemented a dynamic load balancing (choice of 2), described there:

Updates on Test Data

Ok while you are removing any concurrency limit you might have set I will explain how the node selection actually works. When a segment gets commited to the database it will contain the nodes that have been fast enough and it will be missing the nodes that got long tail canceld. The satellite calculates a success rate for each node with that. The node selection takes that success rate. Instead of 110 total nodes it selectes 220 nodes at first and compares them in pairs and pick the one with th…

So, if the success rate is low for your node it’s selected rarely for these uploads.