You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/Usage/NodeTypes.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,20 +10,23 @@ You can run an Archive node, with all history and full lookup for all historical
10
10
11
11
You can run a Full node, with all history and limited lookup for historical transactions. This fits into a 4TB drive and is often the choice for RPC nodes.
12
12
13
-
You can run an Expired node, with pre-merge history and receipts gone. This fits into a 2TB drive and is foten the choice for validator nodes.
13
+
You can run an Expired node, with pre-merge history and receipts gone. This fits into a 2TB drive and is often the choice for validator nodes.
14
14
15
15
This is controlled by variables in `.env`, which can be set with `nano .env`. Switching from one type to another often requires a full resync.
16
16
17
-
`CL_ARCHIVE_NODE` - run the consensus layer node as an archive, including blobs where supported
18
-
`CL_MINIMAL_NODE` - run the consensus layer node with minimal storage
19
-
20
17
`EL_ARCHIVE_NODE` - run the execution layer node as an archive. The required space can vary widely depending on the client: From right around 2 TB to well over 50TB
21
18
`EL_MINIMAL_NODE` - run the execution layer node with history expiry. `true` is pre-merge history expiry; `rolling` is 1-year rolling if the client supports it;
22
-
`aggressive` expires all but the last few blocks, if the client supoorts it
19
+
`aggressive` expires all but the last few blocks, if the client supports it
20
+
21
+
If both variables are set to `false`, you have a Full node.
22
+
23
+
`CL_ARCHIVE_NODE` - run the consensus layer node as an archive, including blobs where supported
24
+
`CL_MINIMAL_NODE` - run the consensus layer node with minimal storage, if the client makes that distinction. See the `--help` for Grandine and Teku, for example,
25
+
with `./ethd cmd run --rm consensus --help`, or directly via `docker run` on their image.
23
26
24
27
## Switch from Full to Expired node
25
28
26
-
You can use `./ethd prune-history` to switch the client to history expiry, in some cases without resync. Note that Besu requires 200 GiB free for this, and
29
+
You can use `./ethd prune-history` to switch the execution layer client to history expiry, in some cases without resync. Note that Besu requires 200 GiB free for this, and
27
30
it will take less space if instead it is resynced with `./ethd resync-execution` while `EL_MINIMAL_NODE=true`
0 commit comments