This is an automated email from the ASF dual-hosted git repository.
guangning pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-manager.git
The following commit(s) were added to refs/heads/master by this push:
new c300c94 Activate BKVM metadata reload at boot (#334)
c300c94 is described below
commit c300c94c8affe9be7ca66b64718f9e2629bd1281
Author: Enrico Olivelli <[email protected]>
AuthorDate: Wed Sep 9 16:13:17 2020 +0200
Activate BKVM metadata reload at boot (#334)
Co-authored-by: Enrico Olivelli <[email protected]>
---
src/main/resources/bkvm.conf | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/main/resources/bkvm.conf b/src/main/resources/bkvm.conf
index 8fe0de7..6863d38 100644
--- a/src/main/resources/bkvm.conf
+++ b/src/main/resources/bkvm.conf
@@ -19,6 +19,10 @@ bkvm.enabled=false
# Default value zk+null://127.0.0.1:2181/ledgers works for Pulsar Standalone
metadataServiceUri=zk+null://127.0.0.1:2181/ledgers
+# Refresh BK metadata at boot.
+# BK metadata are not scanned automatically in BKVM, you have to request it
from the UI
+metdata.refreshAtBoot=true
+
# HerdDB database connection, not to be changed if you are running embedded
HerdDB in Pulsar Manager
# If you are using PostGRE SQL you will have to change this configuration
# We want to use the HerdDB database started by PulsarManager itself, by
default BKVM wants to start its one database
