[
https://issues.apache.org/jira/browse/KARAF-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377597#comment-14377597
]
ASF GitHub Bot commented on KARAF-3628:
---------------------------------------
GitHub user FlavioF opened a pull request:
https://github.com/apache/karaf-cellar/pull/3
[KARAF-3628] Fixed Hazelcast Discovery Service when starting a new
Hazelcast instance
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/FlavioF/karaf-cellar
fix_hazelcast_discovery_service
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/karaf-cellar/pull/3.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3
----
commit 71332ef1a5741dabbd055a002ff87ca093d82e7d
Author: Flávio Ferreira <[email protected]>
Date: 2015-03-20T17:13:02Z
[KARAF-3628] Improved Hazelcast Discovery Service when starting a new
Hazelcast instance
----
> Karaf Hazelcast instance should "merge" the members found by the discovery
> services
> -----------------------------------------------------------------------------------
>
> Key: KARAF-3628
> URL: https://issues.apache.org/jira/browse/KARAF-3628
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-hazelcast
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
>
> Cellar Hazelcast instance tries to discover all members (using the Hazelcast
> network layer configured in the hazelcast.xml). In order to improve the found
> instance, Cellar Hazelcast should bypass the members found by the discovery
> services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)