cerc-io/lighthouse
16
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Fix flag in redundancy docs (#2482)

Browse Source 
Replace all --process-all-attestations with --import-all-attestations

## Issue Addressed

Which issue # does this PR address?

## Proposed Changes

Please list or describe the changes introduced by this PR.

## Additional Info

Please provide any additional information. For example, future considerations
or information useful for reviewers.
This commit is contained in:
SaNNNNNNNN 2021-07-31 02:24:09 +00:00
parent 303deb9969
commit 834ee98bc2
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
book/src/redundancy.md
View File

@ -61,7 +61,7 @@ following flags:
`5052`). This is only required if your backup node is on a different host. `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* - `--subscribe-all-subnets`: ensures that the beacon node subscribes to *all*
subnets, not just on-demand requests from validators. 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. aggregation on all seen attestations.
Subsequently, one could use the following command to provide a backup beacon Subsequently, one could use the following command to provide a backup beacon
@ -72,12 +72,12 @@ lighthouse bn \
--staking \ --staking \
--http-address 0.0.0.0 \ --http-address 0.0.0.0 \
--subscribe-all-subnets \ --subscribe-all-subnets \
--process-all-attestations --import-all-attestations
``` ```
### Resource usage of redundant Beacon Nodes ### 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 cause a significant increase in resource consumption. A doubling in CPU
utilization and RAM consumption is expected. utilization and RAM consumption is expected.