generated from camel.apache.org/component
2
Home
gitea_admin edited this page 2026-03-11 14:43:20 +00:00
Table of Contents
ZooKeeper Master
Have only a single consumer in a cluster consuming from a given endpoint; with automatic failover if the JVM dies.
Metadata
| Property | Value |
|---|---|
| Scheme | zookeeper-master |
| Support Level | Stable |
| Labels | clustering,management,bigdata |
| Version | 4.10.2 |
Maven Dependency
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-zookeeper-master</artifactId>
<version>4.10.2</version>
</dependency>
Endpoint Properties
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
groupName |
string | ✓ | The name of the cluster group to use | |
consumerEndpointUri |
string | ✓ | The consumer endpoint to use in master/slave mode | |
bridgeErrorHandler |
boolean | false |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | |
exceptionHandler |
object | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | ||
exchangePattern |
object | Sets the exchange pattern when the consumer creates an exchange. |