[
https://issues.apache.org/jira/browse/BROOKLYN-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545529#comment-14545529
]
ASF GitHub Bot commented on BROOKLYN-143:
-----------------------------------------
Github user ygy commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/642#issuecomment-102404835
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.
> Add support for Hazelcast
> -------------------------
>
> Key: BROOKLYN-143
> URL: https://issues.apache.org/jira/browse/BROOKLYN-143
> Project: Brooklyn
> Issue Type: New Feature
> Reporter: Yavor Yanchev
> Priority: Minor
>
> Hazelcast is a clustering and highly scalable data distribution platform for
> Java.
> Some of the features it provides
> Distributed java.util.{Queue, Set, List, Map}
> Distributed java.util.concurrency.locks.Lock
> Distributed java.util.concurrent.ExecutorService
> Distributed Indexing and Query support
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
