---

title: Managing brokers

Pulsar brokers consist of two components:

1. An HTTP server exposing a REST interface administration and {% popover topic %} lookup.
2. A dispatcher that handles all Pulsar {% popover message %} transfers.

{% popover Brokers %} can be managed via:

• The brokers command of the pulsar-admin tool
• The /admin/brokers endpoint of the admin REST API
• The brokers method of the {% javadoc PulsarAdmin admin org.apache.pulsar.client.admin.PulsarAdmin %} object in the Java API

In addition to being configurable when you start them up, brokers can also be dynamically configured.

{% include admonition.html type=“info” content=" See the Configuration page for a full listing of broker-specific configuration parameters. " %}

Brokers resources

List active brokers

Fetch all available active brokers that are serving traffic.

pulsar-admin

$ pulsar-admin brokers list use

broker1.use.org.com:8080

REST

{% endpoint GET /admin/brokers/:cluster %}

More info

Java

admin.brokers().getActiveBrokers(clusterName)

list of namespaces owned by a given broker

It finds all namespaces which are owned and served by a given broker.

CLI

$ pulsar-admin brokers namespaces use \
  --url broker1.use.org.com:8080

{
  "my-property/use/my-ns/0x00000000_0xffffffff": {
    "broker_assignment": "shared",
    "is_controlled": false,
    "is_active": true
  }
}

REST

{% endpoint GET /admin/brokers/:cluster/:broker:/ownedNamespaces %}

Java

admin.brokers().getOwnedNamespaces(cluster,brokerUrl);

Dynamic broker configuration

One way to configure a Pulsar {% popover broker %} is to supply a configuration when the broker is started up.

But since all broker configuration in Pulsar is stored in {% popover ZooKeeper %}, configuration values can also be dynamically updated while the broker is running. When you update broker configuration dynamically, ZooKeeper will notify the broker of the change and the broker will then override any existing configuration values.

• The brokers command for the pulsar-admin tool has a variety of subcommands that enable you to manipulate a broker's configuration dynamically, enabling you to update config values and more.
• In the Pulsar admin REST API, dynamic configuration is managed through the /admin/brokers/configuration endpoint.

Update dynamic configuration

pulsar-admin

The update-dynamic-config subcommand will update existing configuration. It takes two arguments: the name of the parameter and the new value. Here's an example for the brokerShutdownTimeoutMs parameter:

$ pulsar-admin brokers update-dynamic-config brokerShutdownTimeoutMs 100

REST API

{% endpoint POST /admin/brokers/configuration/:configName/:configValue %}

More info

Java

admin.brokers().updateDynamicConfiguration(configName, configValue);

List updated values

Fetch a list of all potentially updatable configuration parameters.

pulsar-admin

$ pulsar-admin brokers list-dynamic-config
brokerShutdownTimeoutMs

REST API

{% endpoint GET /admin/brokers/configuration %}

More info

Java

admin.brokers().getDynamicConfigurationNames();

List all

Fetch a list of all parameters that have been dynamically updated.

pulsar-admin

$ pulsar-admin brokers get-all-dynamic-config
brokerShutdownTimeoutMs:100

REST API

{% endpoint GET /admin/brokers/configuration/values %}

More info

Java

admin.brokers().getAllDynamicConfigurations();