Not exact. If they would disable it, all pieces will be deleted right away before moving to the trash, putting the node to the risk to be disqualified, if the satellite would request to restore the trash and will request audits for the restored pieces.
I don’t know… isn’t there a standard period? Is there a way to check it? But why are you asking? I’m lost… to many forum posts😅.
yeap. I just answered on your question. This parameter is regulates how often your node would get an updated stat from the satellites.
1 Like
Trying to edit but I’m getting a 422 error when saving.
I don’t know how it works. I didn’t edited someones wiki either.
Figured out what the error was, this hinted that it maybe was max character count. I had to remove an older version for it to go through.
1 Like
Is it just me or storage.allocated-disk-space: X.0TB in config.yaml is always ignored when using docker? When I specify -e STORAGE="x.0TB" it uses that but without it always defaults to 2.0TB in dashboard.
I was able to move other settings to config.yaml like email/token for instance. I’d prefer most non-networking settings to be self-contained on the disk and do container stop/start to take effect.
This is by design. For some reason they have set it in the dockerfile… 
ENV ADDRESS="" \ EMAIL="" \ WALLET="" \ STORAGE="2.0TB" \ SETUP="false" \ AUTO_UPDATE="true" \ LOG_LEVEL=""
1 Like
Hello @mtone ,
Welcome to the forum!
What token?
Thanks. I meant wallet!
1 Like
Which parameters require the container to be removed and not only restarted?
As far as I know for docker parameters: all of them. Docker is intended to be a disposable/recreatable thing.
Anything in config.yaml will pick up on a restart unless specified/overriden by docker parameters. I think the minimum docker parameters are : all port/directory/user mappings and ADDRESS & STORAGE environment variables.
3 Likes
It would be great if there were parameters that could be changed without restarting or removing the container.
1 Like
That’s how all docker works
1 Like
The node software would have to work differently to be able to change some parameters on runtime. Like number of concurrent uploads for example.
It would be great if that and similar settings could be adjusted dynamically. Then the node could better adapt to current load of the system.
2 Likes
Settings I would like to be able to change during runtime (without stopping the node):
# how many piece delete workers
# storage2.delete-workers: 1
# how many concurrent requests are allowed, before uploads are rejected. 0 represents unlimited.
# storage2.max-concurrent-requests: 0
# how many expired pieces to delete in one batch. If <= 0, all expired pieces will be deleted in one batch.
# collector.expiration-batch-size: 1000
1 Like
It’s a wiki. Anyone can contribute/edit. Mitsos was taking care of it, not me.
2 Likes
I skipped 1.115 since it breaks the dashboard on linux, so I don’t plan on running that version. It’s broken on 1.116 as well, so it may be a while until I update the wiki, I’ll keep running 1.114 long after 1.115 fully rolls out.
1 Like
Which one dashboard?
I started a new node and I see that the list of trust sources web address has changed, from this:
https://www.storj.io/dcs-satellites
to this:
https://static.storj.io/dcs-satellites
Shouldn’t be auto modified in config.yaml of old nodes too?