sandesh-shingare commented on issue #21737:
URL: https://github.com/apache/pulsar/issues/21737#issuecomment-2618146953

   We are facing similar issue in our production cluster where we are using S3 
Offloader. We are using **bookkeeper-first** strategy.
   
   Pulsar version: 4.0.1
   
   Observation: Producers and Consumers were stuck during write/read with 
send/connection timeouts.
   
   `Jan 27 11:40:58 ip-172-23-198-8 pulsar[241767]: 
2025-01-27T11:40:58,481+0000 [BookKeeperClientWorker-OrderedExecutor-2-0] ERROR 
org.apache.bookkeeper.client.PendingReadOp - Read of ledger entry failed: L293 
E0-E0, Sent to [172.23.211.145:3181, 172.23.193.13:3181, 172.23.201.163:3181], 
Heard from [] : bitset = {}, Error = 'No such ledger exists on Bookies'. First 
unread entryis (-1, rc = null)
   Jan 27 12:40:58 ip-172-23-198-8 pulsar[241767]: 2025-01-27T12:40:58,481+0000 
[BookKeeperClientWorker-OrderedExecutor-2-0] ERROR 
org.apache.bookkeeper.client.PendingReadOp - Read of ledger entry failed: L324 
E0-E0, Sent to [172.23.211.145:3181, 172.23.199.169:3181, 172.23.201.163:3181], 
Heard from [] : bitset = {}, Error = 'No such ledger exists on Bookies'. First 
unread entry is (-1, rc = null)
   Jan 27 12:40:58 ip-172-23-198-8 pulsar[241767]: 2025-01-27T12:40:58,481+0000 
[BookKeeperClientWorker-OrderedExecutor-2-0] ERROR 
org.apache.bookkeeper.client.PendingReadOp - Read of ledger entry failed: L324 
E0-E0, Sent to [172.23.211.145:3181, 172.23.199.169:3181, 172.23.201.163:3181], 
Heard from [] : bitset = {}, Error = 'No such ledger exists on Bookies'. First 
unread entry is (-1, rc = null)
   Jan 27 12:40:58 ip-172-23-198-8 pulsar[241767]: 2025-01-27T12:40:58,481+0000 
[BookKeeperClientWorker-OrderedExecutor-2-0] ERROR 
org.apache.bookkeeper.client.PendingReadOp - Read of ledger entry failed: L324 
E0-E0, Sent to [172.23.211.145:3181, 172.23.199.169:3181, 172.23.201.163:3181], 
Heard from [] : bitset = {}, Error = 'No such ledger exists on Bookies'. First 
unread entry is (-1, rc = null)
   `
   
   Thank you for a PR with fix @ethqunzhong.
   
   @lhotari Do we have any timeline around when we are planning to release the 
fix?


-- 
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