Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Merged by Bors] - Fix flag in redundancy docs #2482

Closed
wants to merge 1 commit into from
Closed

[Merged by Bors] - Fix flag in redundancy docs #2482

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions book/src/redundancy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ following flags:
`5052`). This is only required if your backup node is on a different host.
- `--subscribe-all-subnets`: ensures that the beacon node subscribes to *all*
subnets, not just on-demand requests from validators.
- `--process-all-attestations`: ensures that the beacon node performs
- `--import-all-attestations`: ensures that the beacon node performs
aggregation on all seen attestations.

Subsequently, one could use the following command to provide a backup beacon
Expand All @@ -72,12 +72,12 @@ lighthouse bn \
--staking \
--http-address 0.0.0.0 \
--subscribe-all-subnets \
--process-all-attestations
--import-all-attestations
```

### Resource usage of redundant Beacon Nodes

The `--subscribe-all-subnets` and `--process-all-attestations` flags typically
The `--subscribe-all-subnets` and `--import-all-attestations` flags typically
cause a significant increase in resource consumption. A doubling in CPU
utilization and RAM consumption is expected.

Expand Down