{"action":"created","issue":{"url":"https://api.github.com/repos/erlio/vernemq/issues/159","repository_url":"https://api.github.com/repos/erlio/vernemq","labels_url":"https://api.github.com/repos/erlio/vernemq/issues/159/labels{/name}","comments_url":"https://api.github.com/repos/erlio/vernemq/issues/159/comments","events_url":"https://api.github.com/repos/erlio/vernemq/issues/159/events","html_url":"https://github.com/erlio/vernemq/issues/159","id":161704007,"number":159,"title":"Failover Behavior for Clustered Broker System","user":{"login":"hbahn","id":13863157,"avatar_url":"https://avatars.githubusercontent.com/u/13863157?v=3","gravatar_id":"","url":"https://api.github.com/users/hbahn","html_url":"https://github.com/hbahn","followers_url":"https://api.github.com/users/hbahn/followers","following_url":"https://api.github.com/users/hbahn/following{/other_user}","gists_url":"https://api.github.com/users/hbahn/gists{/gist_id}","starred_url":"https://api.github.com/users/hbahn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hbahn/subscriptions","organizations_url":"https://api.github.com/users/hbahn/orgs","repos_url":"https://api.github.com/users/hbahn/repos","events_url":"https://api.github.com/users/hbahn/events{/privacy}","received_events_url":"https://api.github.com/users/hbahn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-06-22T14:51:15Z","updated_at":"2016-06-23T07:42:28Z","closed_at":null,"body":"Hi, There, \r\n\r\nI am afraid that I am bothering all of you. :(\r\n\r\nWe set a clustered system for our broker system. We have been testing many failover cases.\r\nHowever, we have some problems.\r\n\r\nFirst of all, the first testing scenario is like this,\r\n\r\n1. node 1 (on), node 2 (on)\r\n2. node 1 (down forcedly), node 2 (on) - make the node 1 leave from cluster (put the leave command on the node 2) and node 1 (on)\r\n\r\n**[Problem] the cluster does not accept SUBSCRIBE...(other Message types were not tested)\r\n[Action what we did] so before we make node 1 on, we remove all the configuration files (under the directory /var/lib/vernemq) and the cluster is working well.**\r\n**[Point what we concern] is the action (removing the configuration files and offline message under the directory /var/lib/vernemq) safe for resilience broker system?**\r\n\r\nAfter that we tried the failover cases sequentially, \r\n\r\n1. node 1 (on), node 2 (on)\r\n2. node 1 (down), node 2 (on)\r\n3. node 1 (on), node 2 (on)\r\n4. node 1 (on), node 2 (down)\r\n5. node 1 (on), node 2 (on)\r\n6. node 1 (down), node 2 (on)\r\n7. node 1 (on), node 2 (on)\r\n\r\n**[Problem] in the 7th step, we made the node 1 start (vernemq start, and we see that vernemq started properly). However, mqtt clients experienced CONNECT fails after several re-trials the client could CONNECT with cluster (one of nodes)**\r\n**[Action what we did] nothing we can do... just wait..**\r\n\r\nHow can we overcome this problem..?\r\nThanks in advance.\r\n "},"comment":{"url":"https://api.github.com/repos/erlio/vernemq/issues/comments/227974032","html_url":"https://github.com/erlio/vernemq/issues/159#issuecomment-227974032","issue_url":"https://api.github.com/repos/erlio/vernemq/issues/159","id":227974032,"user":{"login":"ioolkos","id":282359,"avatar_url":"https://avatars.githubusercontent.com/u/282359?v=3","gravatar_id":"","url":"https://api.github.com/users/ioolkos","html_url":"https://github.com/ioolkos","followers_url":"https://api.github.com/users/ioolkos/followers","following_url":"https://api.github.com/users/ioolkos/following{/other_user}","gists_url":"https://api.github.com/users/ioolkos/gists{/gist_id}","starred_url":"https://api.github.com/users/ioolkos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ioolkos/subscriptions","organizations_url":"https://api.github.com/users/ioolkos/orgs","repos_url":"https://api.github.com/users/ioolkos/repos","events_url":"https://api.github.com/users/ioolkos/events{/privacy}","received_events_url":"https://api.github.com/users/ioolkos/received_events","type":"User","site_admin":false},"created_at":"2016-06-23T07:42:28Z","updated_at":"2016-06-23T07:42:28Z","body":"I still cannot reproduce problem 2 (delay in connecting after alternate node down).\r\n\r\nHow many clients/connections are on the broker nodes during this test?"}}
{"actor":{"display_login":"ioolkos"}}