Files
palladum-lightning/common
Rusty Russell 5e2f6c5028 gossmap: don't stop reading if we hit a redundant channel_announce.
While this shouldn't happen, it does (pending other fixes), and we stop reading the
gossip store until next time.  The result is partial gossip, demonstrated beautifully
by NicolasDorier's report:

```
lightning_gossipd: gossmap: redundant channel_announce for 864063x1306x1, offsets 1272259 and 1784859!"
```

Gossipd stalld there and don't make more progress.  So gossipd itself
doesn't see the entire gossip_store.

Then things get really batshit:

```
2025-02-04T05:53:28.582Z DEBUG   gossipd: Store compact time: 1429910 msec
```

This took 1429 seconds to process.  Why?

Because it hasn't been processing the gossip store fully, gossipd kept adding "new" records to the end:

```
2025-02-04T05:53:28.583Z DEBUG   gossipd: gossip_store: Read 62716143/1739952/5158256/0 cannounce/cupdate/nannounce/delete from store in 31634458462 bytes, now 31634458440 bytes (populated=true)
```

It has 31GB of gossip in there!  No wonder it took so long...

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Fixes: https://github.com/ElementsProject/lightning/issues/8035
Changelog-Fixed: gossipd: corruption in the gossip_store could cause ever-longer startup times and no gossip updates.
2025-02-11 15:11:47 -06:00
..
2025-02-11 15:11:47 -06:00
2023-09-21 20:08:24 +09:30
2024-08-10 15:20:59 +09:30
2023-06-23 13:12:42 +09:30
2024-07-10 12:21:19 +09:30
2024-03-07 14:09:14 +01:00
2025-02-11 15:11:47 -06:00
2024-11-12 06:42:52 +10:30
2023-09-21 20:08:24 +09:30
2023-07-11 11:41:15 +09:30
2023-07-11 11:41:15 +09:30
2024-10-07 14:05:47 +02:00
2024-10-07 14:05:47 +02:00
2024-02-16 15:02:38 +01:00
2024-11-21 14:15:36 +10:30
2024-11-21 14:15:36 +10:30