[jboss-jira] [JBoss JIRA] (WFCORE-310) Don't copy the contents to all hosts when assigning a deployment to a server-group

[Ken Wills (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102082#comment-13102082 ] 

Ken Wills commented on WFCORE-310:
----------------------------------

I think this comes down to changing the default behavior of ignore-unused-configuration to true from false, with the following modifications:

-  --backup : rename this to --backup-dc (keep --backup around and warn)?

- --cached-dc : an attempt should be made to contact the DC. If this attempt fails the server should still start and log a warning. Possible issues with long timeouts delaying startup, could mitigate with a timeout (still thinking about this one). This behavior is different from current where the initial connection attempt is not made.

- --backup-dc: ignore-unused-configuration is ignored and all content is copied regardless, as this content will potentially be needed should this instance become DC. Using backup should also attempt to contact the DC and ensure everything is pulled & up to date, if this fails it should log & warn (along with last time DC was actually contacted?) but still start.

-- ignore-unused: add this as a command line option, should override value set in host.xml

Only one of --cached-dc or --backup-dc should be set to true, using both should result in an error.

in host.xml: 
        <remote host="${jboss.test.host.master.address}" port="9999" security-realm="ManagementRealm" ignore-unused-configuration="true">

This should allow all of the command line options to be specified:

        <remote host="${jboss.test.host.master.address}" port="9999" security-realm="ManagementRealm" ignore-unused-configuration="false" backup-dc="true" cached-dc="false" >

Do we have use cases for --backup currently where it would be used for anything other than becoming DC? Adding the relevant server groups / using ignore-unused-configuration = false would seem to cover this already.

Also verify a couple of things:

 - if a slave is running with --backup, then it is probably only eligible to become master if it is the same (or >=) version as master(?) We should at least warn in the case this is not true.
 - more? 

> Don't copy the contents to all hosts when assigning a deployment to a server-group
> ----------------------------------------------------------------------------------
>
>                 Key: WFCORE-310
>                 URL: https://issues.jboss.org/browse/WFCORE-310
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Domain Management
>            Reporter: Emanuel Muckenhuber
>            Assignee: Ken Wills
>             Fix For: 2.0.0.CR1
>
>
> When assigning a deployment to a server-group it also copies the actual deployment contents to all hosts regardless of the whether the deployment is used locally or not. This should be changed that the contents are only retrieved if they are actually needed on a local server.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)