[jboss-jira] [JBoss JIRA] (WFLY-1066) Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING)

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-1066:
----------------------------------------

Thanks, Dominik.

We'll need something where servers publish data only when it changes and then they can perform some sort of very simple query to read. Having servers do a complex set of queries to analyze the domain won't scale. For example, JGroups discovery runs periodically, both when a channel connects and when merge protocols like MERGE3 run. So in a large cluster we can't have possibly hundreds of nodes performing multiple ops reading data.

> Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING)
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1066
>                 URL: https://issues.jboss.org/browse/WFLY-1066
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Domain Management
>         Environment: Server running in Domain mode
>            Reporter: Wolf-Dieter Fink
>            Assignee: Tristan Tarrant
>              Labels: clustering, domain, jgroups
>
> It is complicated to keep the subsystem JGroups in sync if the tcp-stack is used in domain mode.
> All new servers that join/leave a clustered server group (configuration) must be added or removed by hand for the jgroup configuration.
> The domain server will receive the informations if a host-controller enrol and register server to a clustered server-group.
> So the configuration of the initial_hosts can be done automaticaly to avoid old entries which cause unnecessary checks and ensure that all active servers are known.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)