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

Configuration of the Arbitrum backfill process #339

Merged
merged 2 commits into from
Jan 17, 2025
Merged

Configuration of the Arbitrum backfill process #339

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
120d897
Environment variables for the backfill process
akolotov Nov 11, 2024
0b51718
Updated default value
akolotov Jan 17, 2025
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
3 changes: 3 additions & 0 deletions setup/env-variables/backend-envs-chain-specific.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,6 +185,9 @@ Supported together with setting `CHAIN_TYPE=arbitrum`
| `INDEXER_ARBITRUM_MISSING_BATCHES_RANGE` | Size of each batch range which will be inspected for the missing batches. Since it is not expected that batches are missed often, it is OK to have this value relatevly large. Implemented in [#10466](https://github.com/blockscout/blockscout/pull/10446). | <p>Version: v6.8.0+<br>Default: <code>10000</code><br>Applications: Indexer</p> |
| `INDEXER_ARBITRUM_CONFIRMATIONS_TRACKING_FINALIZED` | Whether to choose `safe` (true) or `latest` (false) block to discover new confirmations. This setting is required to reduce latency between the actual confirmation transaction and its discovery. Recommended to have true on rollups which use Ethereum Mainnet as L1. Determines how fast new confirmations will be discovered. Implemented in [#9312](https://github.com/blockscout/blockscout/pull/9312). | <p>Version: v6.7.0+<br>Default: <code>true</code><br>Applications: Indexer</p> |
| `INDEXER_ARBITRUM_NEW_BATCHES_LIMIT` | The number of batches to be handled and imported at once. This is applicable for cases when dozens of batches are found in one discovery iteration, and it is necessary to import them in chunks to avoid the entire process being aborted if any errors occur. Implemented in [#9312](https://github.com/blockscout/blockscout/pull/9312). | <p>Version: v6.7.0+<br>Default: <code>10</code><br>Applications: Indexer</p> |
| `INDEXER_ARBITRUM_DATA_BACKFILL_ENABLED` | Enables a process to backfill the blocks and transaction with Arbitrum specific data. This should only be enabled for Arbitrum chains where blocks were indexed before upgrading to a version that includes Arbitrum-specific data indexing features. Implemented in [#11163](https://github.com/blockscout/blockscout/pull/11163). | <p>Version: master<br>Default: <code>false</code><br>Applications: Indexer</p> |
| `INDEXER_ARBITRUM_DATA_BACKFILL_UNINDEXED_BLOCKS_RECHECK_INTERVAL` | The number of L2 blocks to look back in one iteration of the backfill process. Implemented in [#11163](https://github.com/blockscout/blockscout/pull/11163). | <p>Version: master<br>Default: <code>120s</code><br>Applications: Indexer</p> |
| `INDEXER_ARBITRUM_DATA_BACKFILL_BLOCKS_DEPTH` | Interval to retry the backfill task for unindexed blocks. Implemented in [#11163](https://github.com/blockscout/blockscout/pull/11163). | <p>Version: master<br>Default: <code>500</code><br>Applications: Indexer</p> |

## <mark style="background-color:yellow;">Celo Management</mark>

Expand Down