-
Notifications
You must be signed in to change notification settings - Fork 323
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
bug: consensus node panics in concurrent map read-writes #2840
Comments
to add more context from a sync conversation, this seems to occur more frequently the more a node reads from state. |
seems related to cosmos/cosmos-sdk#10568 we might actually need to go in and add a mutex somewhere in the read path I'm curious if this error is always with the distribution keeper or do we see it elsewhere as well? |
Are you sure? It looks like this a concurrency problem in the IAVL not the gRPC server |
yeah I think so, the title of that issue is misleading. its encountering a similar stack trace both from iavl. both scenario's are using the gprc server to read from iavl
|
Summary of Bug
Happened on mainnet for devops infra
RAM consumption was 8Gib which was fine
Version
v1.3.0
Steps to Reproduce
run a node for a while
https://celestia.grafana.net/goto/ath5JDSIg?orgId=1
For Admin Use
The text was updated successfully, but these errors were encountered: