-
Notifications
You must be signed in to change notification settings - Fork 817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR]Moquette clusters #131
Comments
Hi, Andrea
|
Hi Andsel, I need HA basically. Clients would connect to one node of the client. If clients disconnect, they should be responsible of reconnecting and subscribing again to topics. Cluster responsibility would be only to propagate to the nodes message publishing (from broker node to client/s). Example: Nodes A, B, C clients c1 and c2 connect to broker A client c1 publishes message m1 to /t1, then:
Cluster should have not other responsibility. let me know your thoughts. |
What about to use something like Hazelcast for sharing messages on all nodes? |
That's was my intention.
Crating input queues, one for each node. I was planning to keep also
metadata in distributed cache (like which client is connected on which node)
|
Yes. I was thinking in Hazelcast too. |
I've some ideas, I would share it on the google group till I'm finishing to fix the bugs for release 0.8 |
hi,I have some questions.i need cluster,nodes share connections,but channel don't be shared in map.i try to use hazelcat,but i am failure.and i try to use redis to store these connnection channels but i am failure. Could you plz give me some advice,thanks a lot |
hi andsel, i don't know How i can do? |
Hi Andrea On Thu, Feb 4, 2016 at 1:50 AM, 68387097 notifications@github.com wrote:
|
thanks,i used emqttd cluster,but it developedp by erlang,much difficulty to customized.so i want to find a java mqtt-broker-cluster |
Hi these, How about this: https://github.com/mrniko/redisson it's also using netty & redis(opensource) , Hazelcast have both license, opensource it havent persistence store. |
As I understand it's only a Redis' Java client, so you have to install On Tue, May 10, 2016 at 2:32 AM, Chuyen Nguyen notifications@github.com
|
http://ignite.apache.org/ It's pretty cool! |
It's the open version of GridGain, that's quite similar to Hazelcast, and On Fri, Jun 3, 2016 at 12:20 PM, Bin Zhang notifications@github.com wrote:
|
Bumping. Any news? |
I would honestly prefer to create an own solution to detect nodes and connect them with each other like EMQ does. And use Redis for storing subscriptions, session data and more. |
It would be better to design a cluster SPI to allow multiple providers. |
Do you already defined the design of Moquette clustering? |
Bumping. Any news? |
How do I gain access to the group? I cannot find it. Could you please outline a design based on hazelcast? I could work on it and contribute. |
@iiliev2 maybe you could open a new discussion in GH: https://github.com/moquette-io/moquette/discussions |
I need to set a moquette cluster for HA
Does moquette support to work in a cluster environment where several moquette serves share topic, connections and messages?
Regards
The text was updated successfully, but these errors were encountered: