karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From FlavioF <...@git.apache.org>
Subject [GitHub] karaf-cellar pull request: [KARAF-1842] Implemented Service Tracke...
Date Wed, 22 Apr 2015 18:49:09 GMT
GitHub user FlavioF opened a pull request:


    [KARAF-1842] Implemented Service Tracker to remove unavailable distributed service.

    In this PR, it was implemented a Service Tracker to remove unavailable distributed services
from the list of available endpoints. It was implemented taking DiscoveryTask as a reference.
    ###### Modifications in `org/apache/karaf/cellar/hazelcast/HazelcastClusterManager`, `org/apache/karaf/cellar/hazelcast/HazelcastGroupManager`
and `org/apache/karaf/cellar/hazelcast/HazelcastInstanceAware`
    In Hazelcast Cellar bundle updates `getInetSocketAddress().getHostName()` to `getSocketAddress().getHostString()`
when populating cellar nodes since `getHostName()` "may trigger a name service reverse lookup
if the address was created with a literal IP address". It leads to different node IDs depending
if node is running locally  (it will reverse loockup) or not (it will not reverse lockup).
Thus, it is impossible to compare between remote endpoint node IDs (`endpointDescription.getNodes()`)
and cluster manager node IDs (`clusterManager.listNodes()`).
    ###### Modifications in `org/apache/karaf/cellar/hazelcast/HazelcastClusterManager`
    `org/apache/karaf/cellar/hazelcast/QueueConsumer.run` could throw exceptions like OperationTimeoutException.
This could lead to QueueConsumer task being killed making the karaf container useless since
it couldn't communicate. Therefore, when calling `getQueue().poll(10, TimeUnit.SECONDS)` it
now catches all possible Exception to ensure that QueueConsumer task never dies.
    All this changes are needed in order to Service Tracker to work.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/FlavioF/karaf-cellar feature_add_service_tracker_to_unregist_remove_service

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #6
commit de8162fba4542a53050eccf16908981c54131ab6
Author: Flávio Ferreira <fferreira@bikeemotion.com>
Date:   2015-04-22T17:46:42Z

    [KARAF-1842] Implemented Service Tracker to remove unavailable distributed service.


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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message