Thanks @SunDapeng1 for open this issue. currently class PulsarClusterMetadataSetup, which is called by command bin/pulsar initialize-cluster-metadata, will do all the metadata setup for Pulsar.
As discussed here with @murong00 ,
#5879 (comment)
we should make this configuration more easy.

But, Seems in current code, of PulsarClusterMetadataSetup, it is using /ledgers for bookies by default? In your deployment, are you using the localzk as: zkhost:2181/pulsar ? maybe just change it back to zkhost:2181 would solve this issue?

Thank you for your reply. Maybe I didn't describe it clearly. What I want to express is that if the bk metadata is in /ledgers, then when the first pulsar is deployed, the metadata can be initialized to /. At this time, the first pulsar cluster can normally identify /ledgers Bk cluster, but how can I deploy a second pulsar cluster, so that the second pulsar cluster also uses the same bk cluster /ledgers?

@SunDapeng1 , as we discussed, the main issue is make bookie service (/ledgers) configurable. This may involves some change like PulsarClusterMetadataSetup InternalConfigurationData.
at present, ZkLedgersRootPath that passed into InternalConfigurationData is some kind of hard coded.

@jiazhai How is this issue going?