Merger
This page documents the configuration flags for the Merger component. For architectural concepts and how the Merger works, see Merger Architecture.
Starting the Merger
firecore start merger [flags]Core Configuration
--merger-grpc-listen-addr
gRPC listening address for health checks
:10012
Storage Configuration
The Merger uses the common storage flags:
--common-one-block-store-url
One-block files storage URL (input)
file://{data-dir}/storage/one-blocks
--common-merged-blocks-store-url
Merged blocks storage URL (output)
file://{data-dir}/storage/merged-blocks
--common-forked-blocks-store-url
Forked blocks storage URL
file://{data-dir}/storage/forked-blocks
Timing Configuration
--merger-time-between-store-lookups
Polling interval for source store
1s
--merger-time-between-store-pruning
Interval between pruning operations
1m0s
Pruning Configuration
--merger-prune-forked-blocks-after
Blocks to retain before pruning forks
50000
--merger-delete-threads
Parallel threads for file deletion
8
The pruning distance should be set large enough to handle chain reorganizations. The default of 50,000 blocks is conservative and suitable for most chains.
Execution Control
--merger-stop-block
Stop after merging to this block
(none)
Health Check
The Merger exposes a gRPC health check endpoint:
The Merger always reports SERVING status when running - it doesn't have dynamic readiness conditions like other components.
Example Usage
Basic Local Setup
With Cloud Storage
Processing to a Specific Block
Last updated
Was this helpful?
