Sweeper batching allows to control and batch the sweep transactions thereby reducing the impact of high fees for sweeping. However this setting only applies at startup. There can be situation, for example you have a FC with lots of HTLC outputs which you want to consolidate in a single sweep to prevent them swept individually thereby causing high on-chain fees. Today this can be achieved by changing the lnd.conf with desired sweeper.batchwindowduration value and restarting lnd. This is however not a practical approach.
Describe the solution you'd like
In addition to lnd.conf setting, there should be a way to control this parameter at runtime. lncli get and set sweeperbatchwindowduration calls can them be implemented.
Describe alternatives you've considered
Restarting lnd each time a change is required. That is not practical.
Sweeper batching allows to control and batch the sweep transactions thereby reducing the impact of high fees for sweeping. However this setting only applies at startup. There can be situation, for example you have a FC with lots of HTLC outputs which you want to consolidate in a single sweep to prevent them swept individually thereby causing high on-chain fees. Today this can be achieved by changing the lnd.conf with desired sweeper.batchwindowduration value and restarting lnd. This is however not a practical approach.
Describe the solution you'd like
In addition to lnd.conf setting, there should be a way to control this parameter at runtime. lncli get and set sweeperbatchwindowduration calls can them be implemented.
Describe alternatives you've considered
Restarting lnd each time a change is required. That is not practical.