g0715158 opened a new issue, #25055:
URL: https://github.com/apache/pulsar/issues/25055

   ### Search before reporting
   
   - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) 
and found nothing similar.
   
   
   ### Read release policy
   
   - [x] I understand that [unsupported 
versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions)
 don't get bug fixes. I will attempt to reproduce the issue on a supported 
version of Pulsar client and Pulsar broker.
   
   
   ### User environment
   
   version:3.0.10
   jdk 17
   os  arm
   
   ### Issue Description
   
   When I split the snapshot and ledgers directories of the bookie from one 
into four, a problem arises during stress tests with 500KB large messages: file 
reading gets stuck, resulting in extremely low performance. At this time, IO, 
network, and overall CPU utilization are all low, but a single CPU core becomes 
fully saturated. Thread stack analysis shows that the process is blocked in the 
file reading phase.
   
   <!-- Failed to upload "image.png" -->
   
   <!-- Failed to upload "image.png" -->
   
   
   ### Error messages
   
   ```text
   
   ```
   
   ### Reproducing the issue
   
   When I split the snapshot and ledgers directories of the bookie from one 
into four, a problem arises during stress tests with 500KB large messages: file 
reading gets stuck, resulting in extremely low performance. At this time, IO, 
network, and overall CPU utilization are all low, but a single CPU core becomes 
fully saturated. Thread stack analysis shows that the process is blocked in the 
file reading phase.
   
   ### Additional information
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to