How to set up Broker config and other configs like bookie etc

[Muraligowtham]

Hi All, I am new to pulsar and I am creating a pulsar cluster in aws EKS stack using helm charts.I have a question regarding how to set up broker conf and other conf via helm chart. or does it have to be done via java admin client?

can you pls provide clarity on how this can be achieved,

one of the error that i am getting is ,
[Request processing failed; nested exception is org.apache.pulsar.client.admin.PulsarAdminException$NotAllowedException: Topic level policies is disabled, to enable the topic level policy and retry.] with root cause

[lhotari]

Configuring Pulsar Broker and Bookkeeper in Apache Pulsar Helm chart

Here's an example from the pulsar-helm-chart CI tests: https://github.com/apache/pulsar-helm-chart/blob/8ad7cf6b6508a23546a8d5a66e5319cf36f39712/.ci/clusters/values-broker-tls.yaml#L43-L60

# these are values used in pulsar-helm-chart CI, they aren't examples of production settings
bookkeeper:
  replicaCount: 3
  configData:
    diskUsageThreshold: "0.999"
    diskUsageWarnThreshold: "0.999"
    PULSAR_PREFIX_diskUsageThreshold: "0.999"
    PULSAR_PREFIX_diskUsageWarnThreshold: "0.999"

broker:
  replicaCount: 1
  configData:
    ## Enable `autoSkipNonRecoverableData` since bookkeeper is running
    ## without persistence
    autoSkipNonRecoverableData: "true"
    # storage settings
    managedLedgerDefaultEnsembleSize: "1"
    managedLedgerDefaultWriteQuorum: "1"
    managedLedgerDefaultAckQuorum: "1"

For the broker, use the broker.configData key in your values.yaml. If the key is in the default broker.conf file for a particular version of Pulsar (broker.conf for 2.10.3), you can use the key directly.
There are some special cases where the key is missing from the broker.conf or bookkeeper.conf file. In those cases, it's necessary to add PULSAR_PREFIX_ to the configuration key.

The way this works is that a Python script apply-config-from-env.py is used to apply environment variables found in the config file. If there's no match, for a key config, it's necessary to use an environment variable with PULSAR_PREFIX_ to add the new key to the default template config file.
Here's how the pulsar-helm-chart uses apply-config-from-env.py as part of the command for the container:
https://github.com/apache/pulsar-helm-chart/blob/8ad7cf6b6508a23546a8d5a66e5319cf36f39712/charts/pulsar/templates/broker-statefulset.yaml#L204

Example of configuring topicLevelPoliciesEnabled=true in your values.yaml

topicLevelPoliciesEnabled=true requires setting systemTopicEnabled=true.

broker:
  configData:
    systemTopicEnabled: "true"
    topicLevelPoliciesEnabled: "true"

[lhotari]

@Khemendra-Bhardwaj That's a good question. When the key is missing from the conf/broker.conf file, you can add the configs to broker.configData with a key starting with PULSAR_PREFIX_. It's due to the Python script
https://github.com/apache/pulsar/blob/master/docker/pulsar/scripts/apply-config-from-env.py which is used to apply the configuration from the environment. The Apache Pulsar Helm chart uses this script.

[Khemendra-Bhardwaj]

The key is present in conf/broker.conf file in apache pulsar repo
but not in apache pulsar helm repo

key : # Enable/disable automatic bundle unloading for load-shedding
loadBalancerSheddingEnabled=true

Should I add the key :
PULSAR_PREFIX_loadBalancerSheddingEnabled= true
to charts/pulsar/templates/broker-configmap.yaml in pulsar helm repo ?

[lhotari]

Should I add the key :
PULSAR_PREFIX_loadBalancerSheddingEnabled= true
to charts/pulsar/templates/broker-configmap.yaml in pulsar helm repo ?

No. For Helm charts, you usually pass a value.yaml file to configure the options.
In your values.yaml, you could do this:

broker:
  configData:
     loadBalancerSheddingEnabled: "true"

You don't need to have PULSAR_PREFIX_ as the prefix for the key since loadBalancerSheddingEnabled exists in the default conf/broker.conf file in the docker image.

[Khemendra-Bhardwaj]

Should I add the key :
PULSAR_PREFIX_loadBalancerSheddingEnabled= true
to charts/pulsar/templates/broker-configmap.yaml in pulsar helm repo ?

No. For Helm charts, you usually pass a value.yaml file to configure the options. In your values.yaml, you could do this:

broker:
  configData:
     loadBalancerSheddingEnabled: "true"

You don't need to have PULSAR_PREFIX_ as the prefix for the key since loadBalancerSheddingEnabled exists in the default conf/broker.conf file in the docker image.

Hey, I think the issue is best suited to ask here
I need some suggestions regarding my current setup.
I’m running an AWS EKS cluster in the ap-south-1 region with three EC2 instances across different availability zones (1a, 1b, and 1c). Each node hosts a single instance of Bookkeeper, Zookeeper, Broker, and Proxy.
I plan to use AWS EBS for persistent volume provisioning. Specifically, for each node, I will have one AWS EBS volume in the corresponding zone to store Zookeeper and Bookkeeper data (journal and ledgers).
We’re deploying Pulsar using a Helm chart.
Could you provide guidance on how to approach this setup for static volume provisioning , Iike specifying which files and changes are needed.
( Do I need to manually create PV and PVC for each pod of zookeeper and bookeeper and label it to nodes , and specify the mounted path, ? )

[lhotari]

@Khemendra-Bhardwaj when you ask new questions about a different topic please start create a new separate discussion thread. you can add a link to another question if it's relevant to mention.