Repository navigation
Conversation
Document what to expect during the initial Bitcoin mainnet sync: the multi-day indexing and compaction phase, electrs sitting in D state with no new log lines, storage recommendations, how to get progress output (DEBUG=verbose / ELECTRS_ARGS=-vvvv), and using a longer Docker stop timeout so the container can shut electrs and bitcoind down cleanly. Also document the ELECTRS_ARGS passthrough. Closes Blockstream#600 Co-Authored-By: milah-247 <198606151+milah-247@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #600.
This PR updates the README to explain why electrs may appear stuck for several days during its initial Bitcoin mainnet indexing and compaction.
It clarifies that seeing the process in
Dstate, using 0% CPU, and showing no new logs can be normal during this phase. It also adds guidance on storage requirements, enabling more detailed logs to track progress, and increasing Docker's shutdown timeout to prevent the container from stopping too early.This is a documentation-only change, with no code changes.