I know a lot of us have been dealing with full nodes for the past couple of months due to uncollected garbage that’s been sticking around longer than an unwanted houseguest. Since my nodes have been full and unable to store new paid data, I decided to get creative while we wait for the issues with TTL and GC/BF to be sorted out.
Here’s what I did:
Start a new (small) Node: If you’ve got the capacity, consider setting up a new node. It’s like adding a new wing to your data mansion while the old one gets cleaned up.
Exclude Satellites Sending TTL Data: To do this, include one of the following parameters when starting your new node (and remember to always include it, or you’ll risk getting disqualified!).
Watch the data roll in: With the satellite(s) excluded, your new node can start accumulating fresh, paid data without being bogged down by the existing issues.
Trust SLC and/or US1 Satellite later: Once the issues are fixed, simply remove the exclusion parameter and restart your node. The satellite will treat it like a brand new encounter and start sending you data again.
Now, I know this isn’t a one-size-fits-all solution—setting up a new node might not be feasible for everyone. But if you’ve got the extra capacity, this might be a good temporary workaround.
Let’s keep our fingers crossed for a swift resolution and in the meantime, keep those nodes humming!
There is a mistake. US1 might soon have similar load as SLC. So you better start fresh with SLC and US1 excluded and join them later.
My strategy to deal with the open issues is to just ignore them. I do have enough free space so I can just take all uploads I can get even if some of them gets paid at a lower rate. It still is extra money that I don’t want to miss out.
On top of that the SLC uploads are great to test out what I need to change on my end in order to scale my setup and make it work. It gives me a head start over my competitors
Thanks for the heads-up! Looks like we’re dodging more than just one bullet here. Well, then I say let’s fix those issues as soon as possible!
In the meantime, if you’re looking to keep your new node clean and hungry for fresh, paid data, you might want to consider excluding US1 along with SLC. You can do that with this command:
Thank you for the clarification—you’re absolutely right! I wasn’t suggesting that test data isn’t paid, but rather that uncollected garbage, which takes up space, doesn’t earn anything. Thanks for keeping us on track!
Great idea, let’s make sure we cover all our bases! I’ll definitely update the original post to include the US satellite too. Just want to double-check the formatting before I dive in.
@alexey, can you confirm if the command parameter is formatted correctly? Don’t want to send anyone on a wild goose chase!
I would also recommend excluding the eu1 and ap1 satellites, they also have traffic.
On a more serious note, I would welcome a feature to set disk space limits per satellite: let them download stuff, but maybe not necessarily upload new stuff.
This would be nice. To have this ability, I am currently running multiple nodes that are each set to only trust a single satellite.
For anybody thinking about doing this, be aware that the AP1 satellite has very little traffic.
Since the beginning of the month my total stored data for AP1 has only increased by about 3GB, so don’t expect too much right now.
EU1 is a little better. I’ve seen an increase of 28GB of stored data so far this month on my EU1 node. it would take about 3 years to fill a 1 TB hard drive at that rate.
In addition to being a “Temporary Solution for Full Nodes with Uncollected Garbage”, it can also be an interesting option for potato farmers such as myself or people trying to keep their bandwidth usage lower. The US1 satellite has a lot of traffic if AP1 and EU1 are not enough.
The data is not going through satellites, so I do not understand what do you mean. And how the satellite can put customers to the North America?
Do you mean that they do not need to have an USA Visa? Where to sign-up?
Thanks for keeping us on track!
