Este contenido no está disponible en el idioma seleccionado.
Appendix C. Cluster Connection Configuration Elements
The table below lists all of the configuration elements of a cluster-connection
.
Name | Description |
---|---|
address |
Each cluster connection applies only to addresses that match the value specified in the
The
Note You should not have multiple cluster connections with overlapping addresses (for example, "europe" and "europe.news"), because the same messages could be distributed between more than one cluster connection, possibly resulting in duplicate deliveries. |
call-failover-timeout |
Use when a call is made during a failover attempt. The default is |
call-timeout |
When a packet is sent over a cluster connection, and it is a blocking call, |
check-period |
The interval, in milliseconds, between checks to see if the cluster connection has failed to receive pings from another broker. The default is |
confirmation-window-size |
The size, in bytes, of the window used for sending confirmations from the broker connected to. When the broker receives |
connector-ref |
Identifies the |
connection-ttl |
Determines how long a cluster connection should stay alive if it stops receiving messages from a specific broker in the cluster. The default is |
discovery-group-ref |
Points to a |
initial-connect-attempts |
Sets the number of times the system will try to connect a broker in the cluster initially. If the max-retry is achieved, this broker will be considered permanently down, and the system will not route messages to this broker. The default is |
max-hops |
Configures the broker to load balance messages to brokers which might be connected to it only indirectly with other brokers as intermediates in a chain. This allows for more complex topologies while still providing message load-balancing. The default value is |
max-retry-interval |
The maximum delay for retries, in milliseconds. The default is |
message-load-balancing |
Determines whether and how messages will be distributed between other brokers in the cluster. Include the
|
min-large-message-size |
If a message size, in bytes, is larger than |
notification-attempts |
Sets how many times the cluster connection should broadcast itself when connecting to the cluster. The default is |
notification-interval |
Sets how often, in milliseconds, the cluster connection should broadcast itself when attaching to the cluster. The default is |
producer-window-size |
The size, in bytes, for producer flow control over cluster connection. By default, it is disabled, but you may want to set a value if you are using really large messages in cluster. A value of |
reconnect-attempts |
Sets the number of times the system will try to reconnect to a broker in the cluster. If the max-retry is achieved, this broker will be considered permanently down and the system will stop routing messages to this broker. The default is |
retry-interval |
Determines the interval, in milliseconds, between retry attempts. If the cluster connection is created and the target broker has not been started or is booting, then the cluster connections from other brokers will retry connecting to the target until it comes back up. This parameter is optional. The default value is |
retry-interval-multiplier |
The multiplier used to increase the |
use-duplicate-detection |
Cluster connections use bridges to link the brokers, and bridges can be configured to add a duplicate ID property in each message that is forwarded. If the target broker of the bridge crashes and then recovers, messages might be resent from the source broker. By setting |