config(congestion_control) - set max_congestion_missed_chunks to 2 #11473
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.
Setting the max_congestion_missed_chunks to 2. This means that at most 2 (+/-1) chunks worth of outgoing receipts can accumulate before all shards will stop forwarding any receipts to the shard with missing chunks. This is a relatively conservative limit to minimize the impact of incoming receipts on source_receipt_proofs size in the state witness. I expect it to have minimal impact on the total throughput of the chain since it's quite rare to see more than one missed chunk in a row.
It's also worth noting that just having one missed chunk is a special case that will not increase the congestion level:
nearcore/core/primitives/src/congestion_info.rs
Lines 65 to 68 in dd1e278