You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (JIRA)" <ji...@apache.org> on 2017/05/05 14:51:04 UTC
[jira] [Updated] (ARTEMIS-1146) Artemis ServerPlugin support for
Broker state change
[ 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, 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, 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, SCALE UP, SCALE DOWN, etc
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)