nkurihar opened a new issue #981: Cannot connect to a topic because of 
ManagedLedgerException
URL: https://github.com/apache/pulsar/issues/981
 
 
   #### Issue
   
   We sometimes cannot connect to a topic because of `ManagedLedgerException: 
Error while recovering ledger`.
   
   Broker log:
   ```
   [bookkeeper-ml-workers-32-1] WARN  o.a.p.broker.service.BrokerService   - 
Failed to create topic <Topic_Name>
   org.apache.bookkeeper.mledger.ManagedLedgerException: Error while recovering 
ledger
   [bookkeeper-ml-workers-32-1] ERROR o.a.pulsar.broker.service.ServerCnx  - 
[/<Client_IP>:<Client_Port>] Failed to create topic <Topic_Name>
   java.util.concurrent.CompletionException: 
org.apache.pulsar.broker.service.BrokerServiceException$PersistenceException: 
org.apache.bookkeeper.mledger.ManagedLedgerException: Error while recovering 
ledger
       at 
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
 ~[na:1.8.0_131]
   .
   .
   .
   Caused by: org.apache.bookkeeper.mledger.ManagedLedgerException: Error while 
recovering ledger
   [BookKeeperClientWorker-21-1] ERROR o.a.b.client.ReadLastConfirmedOp     - 
While readLastConfirmed ledger: <Ledger_ID> did not hear success responses from 
all quorums
   [bookkeeper-ml-workers-35-1] ERROR o.a.b.mledger.impl.ManagedLedgerImpl - 
[<Topic_Name>] Failed to open ledger <Ledger_ID>: Error while recovering ledger
   ```
   
   Bookie log:
   ```
   [bookie-io-10-2] WARN  o.a.b.proto.ReadEntryProcessor       - Ledger 
<Ledger_ID> fenced by /<Broker_IP>:<Broker_Port>
   ```
   
   When it happens, we have to restart Bookies and/or Brokers.
   If you have seen the same error or have any ideas, please let us know.
   
   #### Steps to reproduce
   Though we have not found how to reproduce yet,
   the following seems to be the trigger:
   * Broker restarting
   * Bookie down
   
   #### System configuration
   * Pulsar version: 1.20.0-incubating
   * BookKeeper version: 4.3.1.72-yahoo
   * Number of Bookies: 3
   * Ensemble size: 2
   * Write quorum size: 2
   * Ack quorum size: 2

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to