-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Standby "H/A" support #372
Comments
Someone with a good insight into the application - how much time do you think, very roughly, would be required to implement something similar as proposed above? |
Basically I agree with your wish. But due to MQTT protocol architecture, implementing duplex system is very difficult. We must care QoS packet proceeding, Retain, session persistence (it's similar but different from your comment's persistence-db), and so on. |
Closing because it's not a bug and there is a great challenge for the cluster on mosquitto-dev ML. |
It would have been great of Mosquitto would have supported an active/standby configuration to make underlaying server maintenance not so scary.
By maybe using file locks to indicate if some of the machines within the "availability cluster" is active.
I'm thinking of a solution where, when you start the Mosquitto process if first verifies it's able to get an exclusive file lock of the "mosquitto.db" in order to proceed. If it's not able to do so, it will keep on running and on a scheduled basis check if the file lock is released and then hook it up and start listening to incoming connections.
The text was updated successfully, but these errors were encountered: