feat: added max-readers flag for db (#17663)

This commit is contained in:
Soubhik Singha Mahapatra
2025-07-29 20:17:59 +05:30
committed by GitHub
parent 6923e051ee
commit 056ae2abce
20 changed files with 63 additions and 3 deletions

View File

@@ -79,6 +79,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
Logging:
--log.stdout.format <FORMAT>
The format to use for logs written to stdout

View File

@@ -43,6 +43,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--table <TABLE>
The table name to diff. If not specified, all tables are diffed.

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
-u, --url <URL>
Specify a snapshot URL or let the command propose a default one.

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--first-block-number <first-block-number>
Optional first block number to export from the db.
It is by default 0.

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--path <IMPORT_ERA_PATH>
The path to a directory for import.

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--no-state
Disables stages that require state.

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--without-evm
Specifies whether to initialize the state without relying on EVM historical data.

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
Logging:
--log.stdout.format <FORMAT>
The format to use for logs written to stdout

View File

@@ -671,6 +671,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
Dev testnet:
--dev
Start the node in dev mode

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
Logging:
--log.stdout.format <FORMAT>
The format to use for logs written to stdout

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--from <FROM>
The height to start at

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
Logging:
--log.stdout.format <FORMAT>
The format to use for logs written to stdout

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
<STAGE>
Possible values:
- headers: The headers stage within the pipeline

View File

@@ -74,6 +74,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
Logging:
--log.stdout.format <FORMAT>
The format to use for logs written to stdout

View File

@@ -67,6 +67,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--metrics <SOCKET>
Enable Prometheus metrics.

View File

@@ -72,6 +72,9 @@ Database:
--db.read-transaction-timeout <READ_TRANSACTION_TIMEOUT>
Read transaction timeout in seconds, 0 means no timeout
--db.max-readers <MAX_READERS>
Maximum number of readers allowed to access the database concurrently
--offline
If this is enabled, then all stages except headers, bodies, and sender recovery will be unwound