{"action":"opened","issue":{"url":"https://api.github.com/repos/fabric8io/fabric8-ipaas/issues/261","repository_url":"https://api.github.com/repos/fabric8io/fabric8-ipaas","labels_url":"https://api.github.com/repos/fabric8io/fabric8-ipaas/issues/261/labels{/name}","comments_url":"https://api.github.com/repos/fabric8io/fabric8-ipaas/issues/261/comments","events_url":"https://api.github.com/repos/fabric8io/fabric8-ipaas/issues/261/events","html_url":"https://github.com/fabric8io/fabric8-ipaas/issues/261","id":144596089,"number":261,"title":"support better load balancing of destinations over brokers","user":{"login":"jstrachan","id":30140,"avatar_url":"https://avatars.githubusercontent.com/u/30140?v=3","gravatar_id":"","url":"https://api.github.com/users/jstrachan","html_url":"https://github.com/jstrachan","followers_url":"https://api.github.com/users/jstrachan/followers","following_url":"https://api.github.com/users/jstrachan/following{/other_user}","gists_url":"https://api.github.com/users/jstrachan/gists{/gist_id}","starred_url":"https://api.github.com/users/jstrachan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jstrachan/subscriptions","organizations_url":"https://api.github.com/users/jstrachan/orgs","repos_url":"https://api.github.com/users/jstrachan/repos","events_url":"https://api.github.com/users/jstrachan/events{/privacy}","received_events_url":"https://api.github.com/users/jstrachan/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/fabric8io/fabric8-ipaas/labels/messaging","name":"messaging","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-30T13:37:24Z","updated_at":"2016-03-30T13:37:24Z","closed_at":null,"body":"when we allocate a destination to a broker it would be nice to use a more fair load balancing technique. e.g. to use some kind of calculation of load (message size on existing queues/topics maybe?) to find the least loaded broker to use? Worst case we should find the one with the least destination count; but then load on a destination will vary wildly so using a better metric would be good."}}