Skip to content

Commit

Permalink
remove references to Prune
Browse files Browse the repository at this point in the history
  • Loading branch information
joaniefromtheblock committed Aug 27, 2024
1 parent b785f2e commit c765963
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 10 deletions.
8 changes: 4 additions & 4 deletions docs/how-to/migrate-database.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ LevelDB2 databases use less memory and proves to be more stable with Teku.

:::caution

We recommend Teku nodes running in [archive mode] use the [automatic migration](#automatic-migration) method, and Teku nodes running in [prune mode] use the [manual migration](#manual-migration).
We recommend Teku nodes running in [`archive` mode] use the [automatic migration](#automatic-migration) method, and Teku nodes running in [`minimal` mode] use the [manual migration](#manual-migration).

:::

Expand Down Expand Up @@ -56,15 +56,15 @@ If migration fails, resolve any issues and retry. Contact support on the [Teku D

## Manual migration

Users can manually migrate Teku nodes running a RocksDB database to a LevelDB2 database if the Teku node runs in [prune mode].
Users can manually migrate Teku nodes running a RocksDB database to a LevelDB2 database if the Teku node runs in [`minimal` mode].

:::caution

Teku nodes running in [archive mode] must resynchronize from genesis to migrate. Use the [automatic migration](#automatic-migration) to migrate Teku nodes running in [archive mode].

:::

To migrate a RocksDB database in [prune mode] to a LevelDB2 database:
To migrate a RocksDB database in [`minimal` mode] to a LevelDB2 database:

1. [Download the latest finalized state] from a beacon node:

Expand Down Expand Up @@ -95,7 +95,7 @@ Teku creates a LevelDB2 database, and starts from the specified recent state. Te
<!-- links -->

[Download the latest finalized state]: https://consensys.github.io/teku/#operation/getEthV1DebugBeaconStatesWithState_id
[prune mode]: ../reference/cli/index.md#data-storage-mode
[`minimal` mode]: ../reference/cli/index.md#data-storage-mode
[archive mode]: ../reference/cli/index.md#data-storage-mode
[supply the finalized checkpoint state]: ../get-started/checkpoint-start.md
[Teku Discord channel]: https://discord.com/invite/consensys
2 changes: 1 addition & 1 deletion docs/how-to/use-rewards-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ The following limitations apply:

- The rewards API relies on state and block data to retrieve the reward information, meaning you'll receive limited data if the beacon node being queried is not an archive node.

- You can only query blocks from finalized to head if you are in `prune` storage mode.
- You can only query blocks from finalized to head if you are in `minimal` storage mode.

## Impact of data storage modes

Expand Down
4 changes: 2 additions & 2 deletions docs/reference/cli/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -428,10 +428,10 @@ data-storage-mode: "archive"

The strategy for handling historical chain data. Valid options are:

- `minimal` - Stores the minimal required data to follow the chain and run validators. Finalized states and historic blocks are pruned.
- `prune` - Stores all blocks, but finalized states are pruned.
- `archive` - Stores all blocks and states.

- `minimal` - Stores the minimal required data to follow the chain and run validators. Finalized states and historic blocks are pruned.

The default is `minimal`.

### `data-storage-non-canonical-blocks-enabled`
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/cli/subcommands/admin.md
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ data-storage-archive-frequency: 1028

Set the frequency (in slots) at which to store finalized states to disk. The default is 2048.

This option is ignored if [`--data-storage-mode`](#data-storage-mode) is set to `prune`.
This option is ignored if [`--data-storage-mode`](#data-storage-mode) is set to `minimal`.

:::note

Expand Down Expand Up @@ -200,7 +200,7 @@ data-storage-mode: "archive"
</TabItem>
</Tabs>

Set the strategy for handling historical chain data. Valid options are `minimal`, `prune` and `archive`. The default is `prune`.
Set the strategy for handling historical chain data. Valid options are `minimal` and `archive`. The default is `minimal`.

#### `data-validator-path`

Expand Down Expand Up @@ -507,7 +507,7 @@ data-storage-mode: "archive"
</TabItem>
</Tabs>

Set the strategy for handling historical chain data. Valid options are `minimal`, `prune` and `archive`. The default is `minimal`.
Set the strategy for handling historical chain data. Valid options are `minimal` and `archive`. The default is `minimal`.

#### `data-validator-path`

Expand Down

0 comments on commit c765963

Please sign in to comment.