murong00 opened a new pull request #13089:
URL: https://github.com/apache/pulsar/pull/13089


   ### Motivation
   
   Currently, the bookkeeper client used by can not be initialized correctly 
when using a separated bookkeeper cluster via `bookkeeperMetadataServiceUri` 
whose zookkeeper connection may be different with pulsar zookkeeper servers.  
e.g.
   ```
   17:08:07.661 [ForkJoinPool.commonPool-worker-43] WARN  
org.apache.bookkeeper.client.RackawareEnsemblePlacementPolicyImpl - Failed to 
find 1 bookies : excludeBookies [], allBookies [].
   17:08:07.662 [ForkJoinPool.commonPool-worker-43] ERROR 
org.apache.bookkeeper.client.LedgerCreateOp - Not enough bookies to create 
ledger with ensembleSize=1, writeQuorumSize=1 and ackQuorumSize=1
   17:08:07.662 [ForkJoinPool.commonPool-worker-43] ERROR 
org.apache.distributedlog.bk.SimpleLedgerAllocator - Error creating ledger for 
allocating 
/kobe/pulsar/packages/function/public/default/redis/v1.0/meta/<default>/allocation
 :
   org.apache.bookkeeper.client.BKException$BKNotEnoughBookiesException: Not 
enough non-faulty bookies available
           at 
org.apache.bookkeeper.client.BKException.create(BKException.java:72) 
~[org.apache.bookkeeper-bookkeeper-server-4.14.3.jar:4.14.3]
           at 
org.apache.distributedlog.BookKeeperClient$1.createComplete(BookKeeperClient.java:223)
 ~[org.apache.distributedlog-distributedlog-core-4.14.3.jar:4.14.3]
           at 
org.apache.bookkeeper.client.LedgerCreateOp.createComplete(LedgerCreateOp.java:272)
 ~[org.apache.bookkeeper-bookkeeper-server-4.14.3.jar:4.14.3]
           at 
org.apache.bookkeeper.client.LedgerCreateOp.initiate(LedgerCreateOp.java:166) 
~[org.apache.bookkeeper-bookkeeper-server-4.14.3.jar:4.14.3]
   ```
   ### Modifications
   
   Use the correct `BKDLConfig` from property `bookkeeperMetadataServiceUri`.
   
   
   


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