-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: Size of channel.db and wtclient.db unchanged since last compacting. #8649
Comments
I don't think changes to |
Thanks for quick response. I run Usually my db grew about 100MB per day. Now constant for two days with 600k updates and I never seen such a behaviour before. Wondering if there was a bigger disk space allocation durcing compactation. |
You just run Are you sure it compacted two days ago? After compaction, did you delete a lot of data (e.g. invoices or payments)? |
Returned immediately ... I am running deletepayments daily via batch. There is a four to five digit number of rebalancing trials daily. And I have activated the following options in lnd.conf gc-canceled-invoices-on-startup=true |
And I closed a lot of channels .. Compactation gain was 1.56x Last compactation was around 4 or 5 weeks before. |
Did you close any channels right after the compaction? Basically what I'm trying to get at: When you delete data in a |
I closed a lot of channels after the compactation in March. But not after the compactation in April. Is it possible that lnd itself marked something as deleted during the startup process after compactation (e.g. invoices) and now using this free space? |
It's possible yes. But unfortunately there is no way to know without shutting down |
I stopped forwarding and rebalancing and compacted a copy of the db with chantools. Channel.db shrinked about another 700MB without any error. Will restart lnd again. |
I think that confirms my theory. Something (700 MB of data) was deleted after compaction, allowing the channel states to grow for 700 MB until actually observable through the file size. With no other indications of something being wrong, I'm closing the issue. Feel free to re-open if anything changes. |
Thank you very. I think the reason was that I haven't restarted lnd for one month. I guess it has deleted a big bunch of data. Often I have some restart between the compactations. |
I compacted the dbs on Saturday. Since then, channel.db and wtclient have not changed. They still have the exact size that was written to the logfile after compacting. Sphinxrelay.db, however, has changed.
I have had about 600,000 state updates since compacting. That's why I don't dare to restart lnd at the moment, because I don't want to end up in a scenario like xmrk with penalties.
Are there things I can check while lnd is running?
Your environment
version of
lnd
v0.16.4-beta
which operating system (
uname -a
on *Nix)5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 (2023-09-29) x86_64 GNU/Linux
version of
btcd
,bitcoind
, or other backendbitcoind
The text was updated successfully, but these errors were encountered: