-
Notifications
You must be signed in to change notification settings - Fork 379
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.
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
SEGV in rocksdb during validator startup #4983
Comments
Given the below line in the backtrace, I think your validator succeeded in unpacking snapshot/rebuilding the Bank and getting through the rest of startup. TransactionStatusService receives work from ReplayStage when transactions are being replayed:
You can determine this from either logs or metrics by looking at the One thing worth noting is that given your commit, you were still running with multi-threaded TSS; we backed that change out in #4875 in order to do some refactoring. So, the change you were running with is no longer present in master. However, we will likely be trying to reintroduce that functionality soon (CC @fkouteib) Given that we will likely try to reintroduce that change (or at least something similar), I am somewhat curious as to the root cause of this. In Discord, you mentioned you had a core dump; you could poke around in there but I'm not really sure what I'd be looking for. Digging up the source in rocksdb could be helpful too, but again, this seems pretty open ended at the moment |
The validator indeed got through loading ledger and then crashed. |
Hmm, can you share what args your validator was running with ? Might be of interest for |
|
Problem
Caught SEGV somewhere in rocksdb arena allocator. Unlikely to be an OOM as node had > 400 GB of free memory at the time of crash.
Validator ID
DmCowGH9DUHYCetfGaWzPzYCi455yDxewcycdyWuPLjx
was reporting metrics to solana.metrics.com, and appears to have crashed immediately after fetching the snapshot.running on commit 0975a9f
Backtrace below:
The text was updated successfully, but these errors were encountered: