|Re: [mosquitto-dev] Advice needed (long, sorry)|
Our clients hit the load balancer initially (ELB on AWS in our case), but with an initial http request (mosquitto can serve these) to the which the node replies with its actual endpoint. The client 'sticks' to that endpoint for its session.The node feeds the ELB with its load so the ELB can choose the least-loaded one.mlOn Wed, Feb 11, 2015 at 5:50 PM, Manuel Domínguez Dorado <manolodd@xxxxxxxxx> wrote:
Hi, thank you.
we have not tried redis. We could try it. But we tried multiple Mosquittos behind haproxy loadbalancing connections to the less occuped broker (instead of roundrobin). There is a problem: as we need persistence (clear session = false), after a disconnection several messages were retained in the broker and the user not allways reconnect to the same broker and therefore the broker cumulates lots of messages that are not longer valid and the client does not receive them after reconnecting. We tried using a brokers frontend line (5 brokers) bridging to a central one. Also, having only the frontend line. But persisted messages are a problem because of sessions, that are exclusive of a single mosquitto.
Maybe it would be good a hook to allow session migration between Mosquittos.
I've also do some proofs having only a Mosquitto with several listener and haproxy roundrobin on their ports. But we did not notice that things went better.
We'll read more about redis. Thank you so much.
mosquitto-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top