[I] LogScanner's consumption latency keeps increasing during cluster upgrades [fluss]

["swuferhong (via GitHub)" <gi...@apache.org>]

swuferhong opened a new issue, #1641:
URL: https://github.com/apache/fluss/issues/1641

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
   
   
   ### Fluss version
   
   main (development)
   
   ### Please describe the bug 🐞
   
   LogScanner's consumption latency keeps increasing during cluster upgrades. It appears the upgrade caused a Netty worker to hang. Fluss currently defaults to only 1 Netty worker thread (`netty.client.num-network-threads`=1), resulting in network channel congestion. The issue disappears when increasing `netty.client.num-network-threads` to 3.
   
   ### Solution
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] LogScanner's consumption latency keeps increasing during cluster upgrades [fluss]

["swuferhong (via GitHub)" <gi...@apache.org>]

swuferhong closed issue #1641: LogScanner's consumption latency keeps increasing during cluster upgrades
URL: https://github.com/apache/fluss/issues/1641


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org