{"action":"created","issue":{"url":"https://api.github.com/repos/erlio/vernemq/issues/84","repository_url":"https://api.github.com/repos/erlio/vernemq","labels_url":"https://api.github.com/repos/erlio/vernemq/issues/84/labels{/name}","comments_url":"https://api.github.com/repos/erlio/vernemq/issues/84/comments","events_url":"https://api.github.com/repos/erlio/vernemq/issues/84/events","html_url":"https://github.com/erlio/vernemq/issues/84","id":132997370,"number":84,"title":"High Availability of a Cluster","user":{"login":"DawoonC","id":6591565,"avatar_url":"https://avatars.githubusercontent.com/u/6591565?v=3","gravatar_id":"","url":"https://api.github.com/users/DawoonC","html_url":"https://github.com/DawoonC","followers_url":"https://api.github.com/users/DawoonC/followers","following_url":"https://api.github.com/users/DawoonC/following{/other_user}","gists_url":"https://api.github.com/users/DawoonC/gists{/gist_id}","starred_url":"https://api.github.com/users/DawoonC/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DawoonC/subscriptions","organizations_url":"https://api.github.com/users/DawoonC/orgs","repos_url":"https://api.github.com/users/DawoonC/repos","events_url":"https://api.github.com/users/DawoonC/events{/privacy}","received_events_url":"https://api.github.com/users/DawoonC/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-11T15:08:06Z","updated_at":"2016-02-12T01:33:55Z","closed_at":null,"body":"I have a cluster with two nodes (**node A** and **node B**).\r\nAnd I had **node B** joined the cluster of **node A**.\r\ne.g. vmq-admin cluster join discovery-node=**node A**\r\n\r\nBelow is the tests I've done to check high availability of my cluster.\r\n\r\n## test 1\r\na client is connected and subscribed to **node B**\r\npublished to **node A**\r\nsuccessfully got message on a client\r\n\r\n## test 2\r\nmanually stopped **node B**\r\npublished to **node A** again\r\nsuccessfully got message on a client (which was connected to **node B** in test 1)\r\n\r\n## test 3\r\nwhile **node B** remain stopped\r\npublished to **node B**\r\nsuccessfully got message on a client\r\n\r\n## test 4\r\nrestarted **node B**\r\nmanually stopped **node A**\r\npublished to **node B**\r\nsuccessfully got message on a client\r\n\r\n## test 5\r\nwhile **node A** remain stopped\r\npublished to **node A**\r\nfailed to publish due to connection error (**node A** is not available)\r\n\r\nThe tests were successful until test 4, but when I stopped **node A**, it did not work as in previous tests.\r\nSo I'm guessing, since **node B** joined the cluster by discovering **node A**, it made **node A** some kind of **\"main node\"** in a cluster. And when the **\"main node\"** is not available, remapping of subscription/connection is not working as perfect as other **\"sub nodes\"**.\r\n\r\nSo I'm wondering if this was an intended behavior, or a misconfiguration of myself."},"comment":{"url":"https://api.github.com/repos/erlio/vernemq/issues/comments/183143497","html_url":"https://github.com/erlio/vernemq/issues/84#issuecomment-183143497","issue_url":"https://api.github.com/repos/erlio/vernemq/issues/84","id":183143497,"user":{"login":"DawoonC","id":6591565,"avatar_url":"https://avatars.githubusercontent.com/u/6591565?v=3","gravatar_id":"","url":"https://api.github.com/users/DawoonC","html_url":"https://github.com/DawoonC","followers_url":"https://api.github.com/users/DawoonC/followers","following_url":"https://api.github.com/users/DawoonC/following{/other_user}","gists_url":"https://api.github.com/users/DawoonC/gists{/gist_id}","starred_url":"https://api.github.com/users/DawoonC/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DawoonC/subscriptions","organizations_url":"https://api.github.com/users/DawoonC/orgs","repos_url":"https://api.github.com/users/DawoonC/repos","events_url":"https://api.github.com/users/DawoonC/events{/privacy}","received_events_url":"https://api.github.com/users/DawoonC/received_events","type":"User","site_admin":false},"created_at":"2016-02-12T01:33:55Z","updated_at":"2016-02-12T01:33:55Z","body":"@dergraf Thanks for quick response! :)\r\n\r\nYes I did stop the node via `vernemq stop`\r\nMy client was connecting to the node directly via public IP\r\n(when I stopped **node B**, auto-reconnecting was not triggered, but when I stopped **node A**, auto-reconnecting was triggered and it failed to reconnect)\r\nAnd my setting is `trade_consistency = on`"}}