From 9eda94a40ef9bc15a4037ec5d1fc96495fd5d289 Mon Sep 17 00:00:00 2001 From: Conner Fromknecht Date: Mon, 15 Jul 2019 14:09:42 -0700 Subject: [PATCH] peer: don't reply if peer's request `initial_graph_sync` We stopped requesting this from other nodes as it is very expensive as the graph continues to grow. In this commit we will also stop responding, as nodes are recommended to begin using the `gossip_queries` and upcoming `extended_gossip_queries` to reconcile missing graph data. --- peer.go | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/peer.go b/peer.go index 7cbd824e..36a6fee7 100644 --- a/peer.go +++ b/peer.go @@ -396,16 +396,6 @@ func (p *peer) initGossipSync() { // bootstrapper to ensure we can find and connect to non-channel // peers. p.server.authGossiper.InitSyncState(p) - - // If the remote peer has the initial sync feature bit set, then we'll - // being the synchronization protocol to exchange authenticated channel - // graph edges/vertexes, but only if they don't know of the new gossip - // queries. - case p.remoteLocalFeatures.HasFeature(lnwire.InitialRoutingSync): - srvrLog.Infof("Requesting full table sync with %x", - p.pubKeyBytes[:]) - - go p.server.authGossiper.SynchronizeNode(p) } }