As explained before, a producer sends a cluster event message in a queue.
On the other hand, each node embeds a consumer. A consumer binds a set of handlers.
The consumer is responsible to get the cluster event messages from the different queues, and depending on the type of the cluster event, the consumer delegates the cluster event to a handler. This means that you have a handler for every type of resource.
For a consumer, we can perform the following tasks:
Check the current status of the consumer (on each node) using the
cluster:consumer-statuscommand, as follows:karaf@root> cluster:consumer-status Node Status [node2:5702 ] [ON ] * [node1:5701 ] [ON ]
The
cluster:consumer-statuscommand accepts a node ID as the argument, as follows:karaf@root> cluster:consumer-status node2:5702 Node Status [node2:5702 ] [ON ]
Stop the consumer of any node using the
cluster:consumer-stop...