[
https://issues.apache.org/jira/browse/ARTEMIS-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated ARTEMIS-1146:
------------------------------------
Description:
Add support to plugins to hook into broker state change.
Ideally, this would allow brokers to know if they are running as a master or
slave at startup and provide signaling for when that state changes
5.x tree API had separate operations, perhaps a single method would make more
sense and allow for any potential future changes?
brokerStateChange(... )
MASTER_BROKER, SLAVE_BROKER, REPLICATION STARTED/COMPLETED,
GRACEFUL_SHUTDOWN, SCALE UP, SCALE DOWN, etc
was:
Add support to plugins to hook into broker state change.
Ideally, this would allow brokers to know if they are running as a master or
slave at startup and provide signaling for when that state changes
5.x tree API had separate operations, perhaps a single method would make more
sense and allow for any potential future changes?
brokerStateChange(... )
MASTER_BROKER, SLAVE_BROKER, REPLICATION STARTED/COMPLETED, SCALE UP, SCALE
DOWN, etc
> Artemis ServerPlugin support for Broker state change
> ----------------------------------------------------
>
> Key: ARTEMIS-1146
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1146
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Matt Pavlovich
>
> Add support to plugins to hook into broker state change.
> Ideally, this would allow brokers to know if they are running as a master or
> slave at startup and provide signaling for when that state changes
> 5.x tree API had separate operations, perhaps a single method would make more
> sense and allow for any potential future changes?
> brokerStateChange(... )
> MASTER_BROKER, SLAVE_BROKER, REPLICATION STARTED/COMPLETED,
> GRACEFUL_SHUTDOWN, SCALE UP, SCALE DOWN, etc
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
