nicoloboschi commented on issue #13967: URL: https://github.com/apache/pulsar/issues/13967#issuecomment-1022163170
There's a draft fix here https://github.com/apache/pulsar/pull/13891 From what I've seen, the DLOG config in ZK is stored twice in two different z-node path, with different `ledgersRootPath` value. `PulsarClusterMetadataSetup` is the first one to put the configuration on ZK and, adding debug, I've seen that it does not pass `/ledgers` as ledgersRootPath value but instead "empty string". (that's why then the Functions Worker tries to search bookies under /available path and not /ledgers/available) I've seen another related problem on the broker side when the BK client is created. The `metadataServiceUri` is computed using `ServiceConfiguration#getBookkeeperMetadataStoreUrl` but it doesn't handle well the ledgersRootPath in the older configuration (only `zookeeperServer` set). See https://github.com/apache/pulsar/blob/a18f8a150b2d5c1af1725f6bf0dcb6582024b0d5/pulsar-broker-common/src/main/java/org/apache/pulsar/broker/ServiceConfiguration.java#L2546-L2583 -- 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]
