gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-04-16 20:39:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update docs for v4.6.0 (#4982)

Browse Source 
* Update DB migration docs

* Document VC broadcast modes

* Update downgrade example (#6)

* update downgrade example

* Add period

* Add v4.1.0

---------

Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
This commit is contained in:
Michael Sproul
2023-12-08 10:45:05 +11:00
committed by GitHub
parent 6c0c41c7ac
commit e02adbf7bf
2 changed files with 77 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
book/src/redundancy.md
View File

@@ -75,7 +75,34 @@ lighthouse bn \
Prior to v3.2.0 fallback beacon nodes also required the `--subscribe-all-subnets` and
`--import-all-attestations` flags. These flags are no longer required as the validator client will
now broadcast subscriptions to all connected beacon nodes by default. This broadcast behaviour
can be disabled using the `--disable-run-on-all` flag for `lighthouse vc`.
can be disabled using the `--broadcast none` flag for `lighthouse vc` (or `--disable-run-on-all`
[deprecated]).
### Broadcast modes
Since v4.6.0, the Lighthouse VC can be configured to broadcast messages to all configured beacon
nodes rather than just the first available.
The flag to control this behaviour is `--broadcast`, which takes multiple comma-separated values
from this list:
- `subscriptions`: Send subnet subscriptions & other control messages which keep the beacon nodes
primed and ready to process messages. It is recommended to leave this enabled.
- `attestations`: Send attestations & aggregates to all beacon nodes. This can improve
propagation of attestations throughout the network, at the cost of increased load on the beacon
nodes and increased bandwidth between the VC and the BNs.
- `blocks`: Send proposed blocks to all beacon nodes. This can improve propagation of blocks
throughout the network, at the cost of slightly increased load on the beacon nodes and increased
bandwidth between the VC and the BNs. If you are looking to improve performance in a multi-BN
setup this is the first option we would recommend enabling.
- `sync-committee`: Send sync committee signatures & aggregates to all beacon nodes. This can
improve propagation of sync committee messages with similar tradeoffs to broadcasting
attestations, although occuring less often due to the infrequency of sync committee duties.
- `none`: Disable all broadcasting. This option only has an effect when provided alone, otherwise
it is ignored. Not recommended except for expert tweakers.
The default is `--broadcast subscriptions`. To also broadcast blocks for example, use
`--broadcast subscriptions,blocks`.
## Redundant execution nodes