{"action":"created","issue":{"url":"https://api.github.com/repos/pika/pika/issues/528","labels_url":"https://api.github.com/repos/pika/pika/issues/528/labels{/name}","comments_url":"https://api.github.com/repos/pika/pika/issues/528/comments","events_url":"https://api.github.com/repos/pika/pika/issues/528/events","html_url":"https://github.com/pika/pika/issues/528","id":59849540,"number":528,"title":"Multiple hosts in connection parameters","user":{"login":"rmb938","id":544545,"avatar_url":"https://avatars.githubusercontent.com/u/544545?v=3","gravatar_id":"","url":"https://api.github.com/users/rmb938","html_url":"https://github.com/rmb938","followers_url":"https://api.github.com/users/rmb938/followers","following_url":"https://api.github.com/users/rmb938/following{/other_user}","gists_url":"https://api.github.com/users/rmb938/gists{/gist_id}","starred_url":"https://api.github.com/users/rmb938/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rmb938/subscriptions","organizations_url":"https://api.github.com/users/rmb938/orgs","repos_url":"https://api.github.com/users/rmb938/repos","events_url":"https://api.github.com/users/rmb938/events{/privacy}","received_events_url":"https://api.github.com/users/rmb938/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/pika/pika/labels/Feature%20Request","name":"Feature Request","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-03-04T19:36:29Z","updated_at":"2015-06-05T23:48:55Z","closed_at":null,"body":"Can you please add a way to give multiple hosts in the connection parameters. If my pika client is connected to a rabbitmq cluster it should be able to failover to the next node in the cluster. The current system does not allow for this functionality."},"comment":{"url":"https://api.github.com/repos/pika/pika/issues/comments/109484152","html_url":"https://github.com/pika/pika/issues/528#issuecomment-109484152","issue_url":"https://api.github.com/repos/pika/pika/issues/528","id":109484152,"user":{"login":"rmb938","id":544545,"avatar_url":"https://avatars.githubusercontent.com/u/544545?v=3","gravatar_id":"","url":"https://api.github.com/users/rmb938","html_url":"https://github.com/rmb938","followers_url":"https://api.github.com/users/rmb938/followers","following_url":"https://api.github.com/users/rmb938/following{/other_user}","gists_url":"https://api.github.com/users/rmb938/gists{/gist_id}","starred_url":"https://api.github.com/users/rmb938/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rmb938/subscriptions","organizations_url":"https://api.github.com/users/rmb938/orgs","repos_url":"https://api.github.com/users/rmb938/repos","events_url":"https://api.github.com/users/rmb938/events{/privacy}","received_events_url":"https://api.github.com/users/rmb938/received_events","type":"User","site_admin":false},"created_at":"2015-06-05T23:48:55Z","updated_at":"2015-06-05T23:48:55Z","body":"Well the cancel on ha failover is called when the queue you're consuming on moves to another node due to failover. So if you have a cluster of node A,B and C and your client is connected to C but the queue is \"living\" on A, if node A fails the queue will get moved to B or C. When that happens node C will tell the client that the queue has failed over. \r\n\r\nHowever if the client is connected to C and that node fails it now has to manually reconnect to another node. The Java client will just try and connect to the next server in the list,reopen the connections (not the channels) and call the consumer cancel event to let the programmer to decide what to do at that point.\r\n\r\nSince pika doesn't do this natively I just keep my own list of servers and when a consumer throws a connection exception I just have it try and open a connection to a server that is next in my list. So this feature is not really a large priority but it would be nice to keep in line on the way the official java client does things."}}