791ba3eb50
This change was largely motivated by an increase in high disk usage as a result of channel update spam. With an in memory graph, this would've gone mostly undetected except for the increased bandwidth usage, which this doesn't aim to solve yet. To minimize the effects to disks, we begin to rate limit channel updates in two ways. Keep alive updates, those which only increase their timestamps to signal liveliness, are now limited to one per lnd's rebroadcast interval (current default of 24H). Non keep alive updates are now limited to one per block per direction. |
||
|---|---|---|
| .. | ||
| bootstrapper.go | ||
| chan_series.go | ||
| gossiper_test.go | ||
| gossiper.go | ||
| log.go | ||
| message_store_test.go | ||
| message_store.go | ||
| mock_test.go | ||
| reliable_sender_test.go | ||
| reliable_sender.go | ||
| sync_manager_test.go | ||
| sync_manager.go | ||
| syncer_test.go | ||
| syncer.go | ||