fix: stabilize Firo node config to prevent RPC deadlocks#3282
Merged
fix: stabilize Firo node config to prevent RPC deadlocks#3282
Conversation
Restrict to IPv4-only to eliminate hanging IPv6 connections, reduce max peer connections (125→40), increase RPC work queue (16→32), and lower dbcache (1024→512) for more frequent flushes.
davidleomay
approved these changes
Feb 27, 2026
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
2 participants
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.
Summary
onlynet=ipv4) to eliminate hanging connections to unreachable IPv6 peersContext
The Firo node was repeatedly freezing due to a cascade: IPv6 connection attempts → socket timeouts → mutex contention → RPC deadlock. See
FIRO-NODE-ANALYSIS.mdfor full root cause analysis.Test plan
socket sending timeoutorNetwork is unreachableerrors