routing+routerrpc: expose mission control parameters in lnd config
This commit exposes the three main parameters that influence mission control and path finding to the user as command line or config file flags. It allows for fine-tuning for optimal results.
This commit is contained in:
10 files changed
+145
-32
No files matched your search
@@ -38,6 +38,7 @@ import (
|
||||
"github.com/lightningnetwork/lnd/lncfg"
|
||||
"github.com/lightningnetwork/lnd/lnpeer"
|
||||
"github.com/lightningnetwork/lnd/lnrpc"
|
||||
"github.com/lightningnetwork/lnd/lnrpc/routerrpc"
|
||||
"github.com/lightningnetwork/lnd/lnwallet"
|
||||
"github.com/lightningnetwork/lnd/lnwire"
|
||||
"github.com/lightningnetwork/lnd/nat"
|
||||
@@ -639,8 +640,13 @@ func newServer(listenAddrs []net.Addr, chanDB *channeldb.DB, cc *chainControl,
|
||||
return link.Bandwidth()
|
||||
}
|
||||
|
||||
// Instantiate mission control with config from the sub server.
|
||||
//
|
||||
// TODO(joostjager): When we are further in the process of moving to sub
|
||||
// servers, the mission control instance itself can be moved there too.
|
||||
s.missionControl = routing.NewMissionControl(
|
||||
chanGraph, selfNode, queryBandwidth,
|
||||
routerrpc.GetMissionControlConfig(cfg.SubRPCServers.RouterRPC),
|
||||
)
|
||||
|
||||
s.chanRouter, err = routing.New(routing.Config{
|
||||
|
||||
Reference in new issue
Block a user