mirror of
https://github.com/sigp/lighthouse.git
synced 2026-03-03 00:31:50 +00:00
fe0cf9cb67
Related to #6880, an issue that's usually observed on local devnets with small number of nodes. When testing range sync, I usually shutdown a node for some period of time and restart it again. However, if it's within `SYNC_TOLERANCE_EPOCHS` (8), Lighthouse would consider the node as synced, and if it may attempt to produce a block if requested by a validator - on a local devnet, nodes frequently produce blocks - when this happens, the node ends up producing a block that would revert finality and would get disconnected from peers immediately. NOTE: This is PR#7030 cherry-picked from `unstable` to `release-v7.0.0`. Run Lighthouse BN with this flag to override: ``` --sync-tolerance--epoch 0 ```
29 lines
843 B
YAML
29 lines
843 B
YAML
participants:
|
|
- cl_type: lighthouse
|
|
cl_image: lighthouse:local
|
|
cl_extra_params:
|
|
- --subscribe-all-data-column-subnets
|
|
- --subscribe-all-subnets
|
|
# Note: useful for testing range sync (only produce block if node is in sync to prevent forking)
|
|
- --sync-tolerance-epochs=0
|
|
- --target-peers=3
|
|
count: 2
|
|
- cl_type: lighthouse
|
|
cl_image: lighthouse:local
|
|
cl_extra_params:
|
|
# Note: useful for testing range sync (only produce block if node is in sync to prevent forking)
|
|
- --sync-tolerance-epochs=0
|
|
- --target-peers=3
|
|
count: 2
|
|
network_params:
|
|
electra_fork_epoch: 1
|
|
fulu_fork_epoch: 2
|
|
seconds_per_slot: 6
|
|
snooper_enabled: false
|
|
global_log_level: debug
|
|
additional_services:
|
|
- dora
|
|
- spamoor_blob
|
|
- prometheus_grafana
|
|
dora_params:
|
|
image: ethpandaops/dora:fulu-support |