[
https://issues.apache.org/jira/browse/IGNITE-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933390#comment-15933390
]
Edward Capriolo edited comment on IGNITE-4837 at 3/20/17 7:47 PM:
------------------------------------------------------------------
Thanks for the reply. There are a few benefits of the Gossip based discovery
* gossip is light weight, small code/memory/cpu footprint
* no need need a third party "move the problem" system. IE separate filesystem,
database, etc.
I believe the gossip implementation would be close in characteristic
multicast/jclouds implementation. (Gossip does not use multicast)
I was looking at the zookeeper one as a starting point. It should not take me
too long to figure out but I need to ramp up on my ignite knowledge a little
bit. I am willing to do the legwork if you would like to make me the assignee.
was (Author: appodictic):
Thanks for the reply. There are a few benefits of the Gossip based discovery
* gossip is light weight, small code/memory/cpu footprint
* no need need a third party "move the problem" system. IE separate filesystem,
database, etc.
I believe the gossip implementation would be close in characteristic
multicast/jclouds implementation. (Gossip does not use multicast)
I was looking at the zookeeper one as a starting point. It should not take me
too long to figure out but I need to ramp up on my ignite knowledge a little
bit.
> Apache Gossip based discovery
> ------------------------------
>
> Key: IGNITE-4837
> URL: https://issues.apache.org/jira/browse/IGNITE-4837
> Project: Ignite
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Priority: Minor
>
> I notice that ignite has a few systems for node discovery.
> http://gossip.incubator.apache.org/ is finishing it's second release and I
> would like to see if the ignite community believes Gossip can be used as a
> discovery layer. On the surface a no SPOF system like Gossip seems like a
> good fit but I am still ramping up as to what the specific requirements for
> ignite would be.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
