-
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
high memory usage when connected to bitcoind undergoing initial block download #1218
Comments
So you're attempting to sync |
I don't know what |
In the normal case it doesn't. I have an
To re-word my comment above: one should allow their If you're able to reproduce this, if you run with the |
I think this bug related with this: |
Here's a description showing the same bug: https://medium.com/andreas-tries-blockchain/bitcoin-lightning-network-1-can-i-compile-and-run-a-node-cd3138c68c15 |
Yes the issue is that during IDB, due to the bounded queue of RPC requests, bitcoind can't keep up with out requests. As a result, it drops them and we currently don't retry for those assuming that bitcoind is "trusted". A temp work around would be increasing the size of the RPC work queue. |
No longer an issue as of #3141. |
Background
I just installed lnd with bitcoind on mainnet. After bitcoind finished reindexing (due to txindex) , the RAM usage of lnd increased steadily to more than 30 GByte (on a system with 128 GByte RAM).
The last few log messages (trace):
Your environment
lnd
: lnd version 0.4.1-betauname -a
on *Nix): Linux ftp 4.9.0-3-amd64 Fix name typo in README #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linuxbtcd
,bitcoind
, or other backend: Bitcoin Core Daemon version v0.16.0Steps to reproduce
Start bitcoind with reindex and txindex=1, start lnd, wait
Expected behaviour
Less memory consumption. I also notice other log messages now (gossip?) that did not appear before the forced restart.
Actual behaviour
High memory consumption, steadily growing.
The text was updated successfully, but these errors were encountered: