Closed kroese closed 2 years ago
https://github.com/itsneski/lightning-jet#config-file, exclude
setting under rebalancer section allows you to disable rebalancer for individual peers.
to disable the rebalancer for all peers, you will need to stop the main process and the rebalancer:
jet stop daddy
jet stop rebalancer
Thanks, but when the container is restarted (after I reboot the host for example) it will be running again I guess? So still it would be better if I could persist this in the config file, else I have to repeat these steps every time.
rebalancer won't be running when the container is restarted unless you made the main process (daddy) a system daemon that automatically starts up upon system restart.
with that being said, there is a use case when the rebalancer needs to be disabled while other services (logger, telegram) are running. i will introduce an explicit disable
flag under the rebalancer config section.
for now, make sure that daddy & rebalancer services aren't running (by simply not starting them in the container).
I just tried it, I stopped both services. But when I restarted the container both were running again?
I didnt add them as a system daemon as far as I remember.
I presume you started the container as in https://github.com/itsneski/lightning-jet#start-up-daddy, correct? this will start up the daddy process. so the disable
flag is needed in this case to ensure that the rebalancer isn't running. the flag will be introduced in the upcoming release (1.4.4).
in the meantime, the workaround is to stop daddy and rebalancer manually.
part of jet 1.4.4 release
Is there any option to disable the auto balancer? For example, if you use it just for analyze-fees or some other function.
One workaround I can think of is to raise the minimal required channelsize to a very high number so that all channels get excluded, but it would be nicer to just have a dedicated flag for this.