Performance degradation for staked connections (SWQoS) in version 2.1.9

[StaRkeSolanaValidator]

Problem Description

After upgrading to 2.1.9, our validator has experienced significant performance degradation related to staked connections (SWQoS). The primary issue observed is not being able to stablish a estable QUIC connection between the RPC and Validator, which return the following error log on the RPC side:

"ERR: Application error 0x5 (remote): invalid_stream"

Validator details:

• Validator Identity: 3s97yjq2MhoPVPC3U9VeE3Z5S643Pweovg88ysvrQPw5
• Version: 2.1.9
• No relayer

Note: Once the Validator is rolled back to 2.0.22, the normal behaviour is immediately established.

Proposed Solution

No actual proposal beyond assessing what is triggering this issue in 2.1.x, however I would urge to identify the root cause before Solana Foundation call the 2.1.x for the whole cluster or when 2.0.x is forked, as it is widely used by major RPC providers.

[StaRkeSolanaValidator]

Same behaviour detected in 2.1.11

[StaRkeSolanaValidator]

This issue seems to start associated with this commit

Based on the commit, this is not really an issue. The behavoiur is correct and the SWQoS partner should not exceed the Maximum transaction size.

[alessandrod]

Hey @StaRkeSolanaValidator can you tell me more about how your swqos partner is sending txs? What client are they using? Are they using a custom client? Is it open source so I can review it?

[StaRkeSolanaValidator]

Hey @StaRkeSolanaValidator can you tell me more about how your swqos partner is sending txs? What client are they using? Are they using a custom client? Is it open source so I can review it?

Not sure the client they are using, I will dig into it. Thanks for replying!