Using redis for cluster discovery and shared data.

[Sandeep Bagchi]

Hi, 

I'm trying to implement a vert.x only solution. 

Two nodes running on separate machines. Having a common redis cache.

Both expose http server verticle() and event bus verticle (i intend event bus to be shared)

For clustering as vert.x event doesn't use communication library of hazelcast or inifinispan etc.

I plan to implement cluster manager where nodes are discovered via redis (particular key to be set) 

I pointers in library that be used for serializing data for AsyncMultimap and Map(Async/Sync).

Thanks

Sandeep

[Julien Viet]

hi,

looks like a very interesting project, please keep us aware of the progress in this list!

Julien

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/d0e49729-9e97-4973-9d2f-0130c4ea6fd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sandeep Bagchi]

Hi Julien, 

I have started working on this. Initial commit at https://github.com/thebagchi/vertx-redisbackend-clustermanager

[Sandeep Bagchi]

Hi 

Initial working version using jedis updated in git repository.

AsyncMultiMap  has a near cache using guava for quicker access of ChoosableIterable.

Pubsub used for notifying nodes upon joining, leaving, node active and near cache updates.

Issues:: upon node leaving, asyncmmap having vertx_subs set is not updated. Thus event bus is trying to send to node already left.

Sandeep

[Paulo Lopes]

Hi,

That looks nice I guess the next steps would be to use the vertx redis client as it would avoid all the execute blocking calls making it truly async !

Anyway, good work!