brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ygy <>
Subject [GitHub] incubator-brooklyn pull request: BROOKLYN-143 - Initial support fo...
Date Fri, 15 May 2015 13:54:44 GMT
Github user ygy commented on the pull request:
    This part of the implementation is not finalized yet. It is using TCP/IP autodiscovery.

    By default, TCP/IP autodiscovery requires only one (well known) member. Additional nodes
(members) use it to know about each other. Once a new member connect to the "known-member",
it will receive the information for all the other members of the cluster. 
    Current implementation is suitable for development purposes, but not for real production
environment. I will extend it soon, adding some tests as well.
    On the other hand side, Hazelcast doesn't provide a cli tool for adding new members. Nodes
configuration is described in the config file (hazelcast.xml). Adding a new node (member)
should be added in the config on every single node. Additionally, It requires node restart
when configuration is changed. I'm still trying to figure out the correct way for editing
and applying multiple configurations of already running services in Brooklyn.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message