dragonls commented on issue #15108:
URL: https://github.com/apache/pulsar/issues/15108#issuecomment-1103828450

   Seeing new phenomenon of logs:
   ```
   15:05:32.148 [bookkeeper-ml-scheduler-OrderedScheduler-0-0] WARN  
org.apache.pulsar.broker.service.persistent.PersistentTopic - 
[persistent://euler/train/mid_100481-partition-20] Failed to persist msg in 
store: java.util.concurrent.CompletionException: 
org.apache.pulsar.metadata.api.MetadataStoreException: 
org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = 
Session expired for 
/managed-ledgers/euler/train/persistent/mid_100481-partition-20
   
   15:07:32.578 [ForkJoinPool.commonPool-worker-27] WARN  
org.apache.pulsar.broker.service.ServerCnx - [/9.166.135.165:56492] Failed to 
add producer to topic persistent://euler/train/mid_100481-partition-20: 
producerId=916, Topic is temporarily unavailable
   15:07:32.578 [BookKeeperClientWorker-OrderedExecutor-16-0] WARN  
org.apache.pulsar.broker.service.persistent.PersistentTopic - 
[persistent://euler/train/mid_100481-partition-20] Failed to persist msg in 
store: Bookie operation timeout
   15:07:32.442 [BookKeeperClientWorker-OrderedExecutor-16-0] INFO  
org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl - 
[euler/train/persistent/mid_100481-partition-20] Ledger creation was initiated 
120010 ms ago but it never completed and creation timeout task didn't kick in 
as well. Force to fail the create ledger operation.
   15:07:32.442 [BookKeeperClientWorker-OrderedExecutor-16-0] ERROR 
org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl - 
[euler/train/persistent/mid_100481-partition-20] Error creating ledger rc=-23 
Bookie operation timeout
   ```
   which makes the topic `temporarily unavailable`. Just the same as #14333.
   
   `topicFencingTimeoutSeconds>0` is useless this time.


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