Changelog v0.26.3

[littleskunk]

storj/storj

[Odmin]

I pay you attention for storage2.max-concurrent-requests on config.yaml again.

I commented this line on config.yaml but default value is not unlimited and I have rejected pieces:

docker logs storagenode 2>&1 | grep "reje"
2019-11-25T07:40:22.831Z ERROR piecestore upload rejected, too many requests {"live requests": 8}

@littleskunk

Remove default concurrency limit

By default a storage node had a limit of 6 concurrent transfers and will reject additional uploads until one of the ongoing transfers is finished. We believe with dRPC the limit is not needed anymore. By default the storage nodes will now take as many uploads as they can. You can still set the limit in your config file like before. Removing it from the config will reset it to the new default value.
Changelog v0.24.5

Last release only halve of that change was released. This time the change is real. In addition to that we also increase the audit timeout from 25s to 5 minutes to avoid disqualifications for responding too slow. If you haven’t already please remove any limit you might have set in your config file . We want to test the limits of dRPC.

So, this change is not working.

[will.topping]

my nodes haven’t updated? Is there an issue?

[Pentium100]

I get this when trying to update (current version 0.26.2)

alpha: Pulling from storjlabs/storagenode
Digest: sha256:311d4f2d8b57b02d9dafd0c4b15c06d1aec84756211ed6b7e57a7e01949286ef
Status: Image is up to date for storjlabs/storagenode:alpha
dac528f62f38cd98c2a479842f9ff3b95d1d4d633cac17648813fd9d4125ceb5

[darthShadow]

The tags don’t seem to have been updated for this release. Beta still points to v0.26.2

[BrightSilence]

The only update mentioned for storagenode is:

• storagenode/updater: read identity location from storagenode’s config.yaml (#3607)

That only applies to windows nodes, so I’m guessing there is no update for docker nodes.

[HeroHann]

Can someone have a look over here: Still Offline

[littleskunk]

@Odmin

I commented this line on config.yaml but default value is not unlimited and I have rejected pieces:

Unlimited for dRPC requests. For backwards compatibility the default for gRPC is still there. And we better keep it that way because gRPC is able to kill storage nodes.

[Odmin]

Thanks a lot @littleskunk!
Now it completely clear for me.