[jboss-jira] [JBoss JIRA] (WFCORE-298) Provide configuration to define when config changes are pushed to servers in a domain
Brian Stansberry (JIRA)
issues at jboss.org
Fri Mar 10 13:35:00 EST 2017
[ https://issues.jboss.org/browse/WFCORE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated WFCORE-298:
------------------------------------
Affects Version/s: domain-mode
> Provide configuration to define when config changes are pushed to servers in a domain
> -------------------------------------------------------------------------------------
>
> Key: WFCORE-298
> URL: https://issues.jboss.org/browse/WFCORE-298
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: domain-mode
> Reporter: Brian Stansberry
> Labels: EAP
>
> An EAP customer request:
> Right now, any changes done via the CLI to an active profile are pushed to all instances immediately. Some go life, some at reload only
> While batch mode can be used to bundle a number of changes in one go, there is currently no way to tell individual servers or server-groups when to accept updates or not.
> This proposal is to allow a config switch on servergroup level and on individual server level to accept a configuration change selectively:
> 1. immediate, the current situation, being the default
> 2. at restart only
> 3. at explicit being told so, e.g. when a "reload" is ordered
> Example:
> <server name="server-three" group="other-server-group" updates="immediate">
> the default when the attribute is absent
> <server name="server-three" group="other-server-group" updates="start">
> <server name="server-three" group="other-server-group" updates="explicit">
> The latter could then be triggered with:
> /host=master/server-config=server1:reload
> Similar option could be set on servergroup level, with a similar reload command on that level
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list