Pulsar configuration can be managed either via a series of configuration files contained in the conf directory of a Pulsar installation

• BookKeeper
• Broker
• Client
• Service discovery
• Log4j
• Log4j shell
• Standalone
• WebSocket
• ZooKeeper

BookKeeper

BookKeeper 是一个冗余的日志存储系统，Pulsar 用它来持久化存储所有消息。

Broker

Pulsar broker 负责处理从生产者发出的消息、向消费者派发消息、在集群间复制数据，等等。

• Either the max rollover time has been reached
• or max entries have been written to the ledged and at least min-time has passed | 50000 | | managedLedgerMinLedgerRolloverTimeMinutes | Minimum time between ledger rollover for a topic | 10 | | managedLedgerMaxLedgerRolloverTimeMinutes | Maximum time before forcing a ledger rollover for a topic | 240 | | managedLedgerCursorMaxEntriesPerLedger | Max number of entries to append to a cursor ledger | 50000 | | managedLedgerCursorRolloverTimeInSeconds | Max time before triggering a rollover on a cursor ledger | 14400 | | managedLedgerMaxUnackedRangesToPersist | Max number of “acknowledgment holes” that are going to be persistently stored. When acknowledging out of order, a consumer will leave holes that are supposed to be quickly filled by acking all the messages. The information of which messages are acknowledged is persisted by compressing in “ranges” of messages that were acknowledged. After the max number of ranges is reached, the information will only be tracked in memory and messages will be redelivered in case of crashes. | 1000 | | autoSkipNonRecoverableData | Skip reading non-recoverable/unreadable data-ledger under managed-ledger’s list.It helps when data-ledgers gets corrupted at bookkeeper and managed-cursor is stuck at that ledger. | false | | loadBalancerEnabled | Enable load balancer | true | | loadBalancerPlacementStrategy | Strategy to assign a new bundle weightedRandomSelection | | | loadBalancerReportUpdateThresholdPercentage | Percentage of change to trigger load report update | 10 | | loadBalancerReportUpdateMaxIntervalMinutes | maximum interval to update load report | 15 | | loadBalancerHostUsageCheckIntervalMinutes | Frequency of report to collect | 1 | | loadBalancerSheddingIntervalMinutes | Load shedding interval. Broker periodically checks whether some traffic should be offload from some over-loaded broker to other under-loaded brokers | 30 | | loadBalancerSheddingGracePeriodMinutes | Prevent the same topics to be shed and moved to other broker more that once within this timeframe | 30 | | loadBalancerBrokerMaxTopics | Usage threshold to allocate max number of topics to broker | 50000 | | loadBalancerBrokerUnderloadedThresholdPercentage | Usage threshold to determine a broker as under-loaded | 1 | | loadBalancerBrokerOverloadedThresholdPercentage | Usage threshold to determine a broker as over-loaded | 85 | | loadBalancerResourceQuotaUpdateIntervalMinutes | Interval to update namespace bundle resource quotat | 15 | | loadBalancerBrokerComfortLoadLevelPercentage | Usage threshold to determine a broker is having just right level of load | 65 | | loadBalancerAutoBundleSplitEnabled | enable/disable namespace bundle auto split | false | | loadBalancerNamespaceBundleMaxTopics | maximum topics in a bundle, otherwise bundle split will be triggered | 1000 | | loadBalancerNamespaceBundleMaxSessions | maximum sessions (producers + consumers) in a bundle, otherwise bundle split will be triggered | 1000 | | loadBalancerNamespaceBundleMaxMsgRate | maximum msgRate (in + out) in a bundle, otherwise bundle split will be triggered | 1000 | | loadBalancerNamespaceBundleMaxBandwidthMbytes | maximum bandwidth (in + out) in a bundle, otherwise bundle split will be triggered | 100 | | loadBalancerNamespaceMaximumBundles | maximum number of bundles in a namespace | 128 | | replicationMetricsEnabled | Enable replication metrics | true | | replicationConnectionsPerBroker | Max number of connections to open for each broker in a remote cluster More connections host-to-host lead to better throughput over high-latency links. | 16 | | replicationProducerQueueSize | Replicator producer queue size | 1000 | | replicatorPrefix | Replicator prefix used for replicator producer name and cursor name pulsar.repl | | | replicationTlsEnabled | Enable TLS when talking with other clusters to replicate messages | false | | defaultRetentionTimeInMinutes | Default message retention time | | | defaultRetentionSizeInMB | Default retention size | 0 | | keepAliveIntervalSeconds | How often to check whether the connections are still alive | 30 | | brokerServicePurgeInactiveFrequencyInSeconds | How often broker checks for inactive topics to be deleted (topics with no subscriptions and no one connected) | 60 | | loadManagerClassName | Name of load manager to use | org.apache.pulsar.broker.loadbalance.impl.SimpleLoadManagerImpl | | managedLedgerOffloadDriver | Driver to use to offload old data to long term storage (Possible values: S3) | | | managedLedgerOffloadMaxThreads | Maximum number of thread pool threads for ledger offloading | 2 | | s3ManagedLedgerOffloadRegion | For Amazon S3 ledger offload, AWS region | | | s3ManagedLedgerOffloadBucket | For Amazon S3 ledger offload, Bucket to place offloaded ledger into | | | s3ManagedLedgerOffloadServiceEndpoint | For Amazon S3 ledger offload, Alternative endpoint to connect to (useful for testing) | | | s3ManagedLedgerOffloadMaxBlockSizeInBytes | For Amazon S3 ledger offload, Max block size in bytes. (64MB by default, 5MB minimum) | 67108864 | | s3ManagedLedgerOffloadReadBufferSizeInBytes | For Amazon S3 ledger offload, Read buffer size in bytes (1MB by default) | 1048576 |

Client

The pulsar-client CLI tool can be used to publish messages to Pulsar and consume messages from Pulsar topics. This tool can be used in lieu of a client library.

Service discovery

Log4j

Log4j shell

Standalone

WebSocket

Pulsar proxy

The Pulsar proxy can be configured in the conf/proxy.conf file.

ZooKeeper

ZooKeeper handles a broad range of essential configuration- and coordination-related tasks for Pulsar. The default configuration file for ZooKeeper is in the conf/zookeeper.conf file in your Pulsar installation. The following parameters are available:

In addition to the parameters in the table above, configuring ZooKeeper for Pulsar involves adding a server.N line to the conf/zookeeper.conf file for each node in the ZooKeeper cluster, where N is the number of the ZooKeeper node. Here’s an example for a three-node ZooKeeper cluster:

server.1=zk1.us-west.example.com:2888:3888
server.2=zk2.us-west.example.com:2888:3888
server.3=zk3.us-west.example.com:2888:3888

We strongly recommend consulting the ZooKeeper Administrator’s Guide for a more thorough and comprehensive introduction to ZooKeeper configuration