{"action":"created","issue":{"url":"https://api.github.com/repos/odesk/phystrix/issues/19","repository_url":"https://api.github.com/repos/odesk/phystrix","labels_url":"https://api.github.com/repos/odesk/phystrix/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/odesk/phystrix/issues/19/comments","events_url":"https://api.github.com/repos/odesk/phystrix/issues/19/events","html_url":"https://github.com/odesk/phystrix/issues/19","id":180320083,"number":19,"title":"StateStorage for redis","user":{"login":"gabel","id":242039,"avatar_url":"https://avatars.githubusercontent.com/u/242039?v=3","gravatar_id":"","url":"https://api.github.com/users/gabel","html_url":"https://github.com/gabel","followers_url":"https://api.github.com/users/gabel/followers","following_url":"https://api.github.com/users/gabel/following{/other_user}","gists_url":"https://api.github.com/users/gabel/gists{/gist_id}","starred_url":"https://api.github.com/users/gabel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gabel/subscriptions","organizations_url":"https://api.github.com/users/gabel/orgs","repos_url":"https://api.github.com/users/gabel/repos","events_url":"https://api.github.com/users/gabel/events{/privacy}","received_events_url":"https://api.github.com/users/gabel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-30T14:37:14Z","updated_at":"2016-09-30T15:26:19Z","closed_at":null,"body":"With multiple load balanced nodes on a non apc shared environment the circuit breaker storage could be shared between them. The alternative is that all instances of the same service have their own circuit state storage. A shared storage would generate overhead due to network communication but may be appropriate in some setups.\r\n\r\nAny plans to create or support a PR for state storages for redis or others to support multi-node environments or setups without apc/apcu? \r\n\r\n**Update**\r\n\r\nThis brings me to the question how to use the dashboard for multiple instances of one service - but maybe this topic belongs in the dashboard component issues..."},"comment":{"url":"https://api.github.com/repos/odesk/phystrix/issues/comments/250774259","html_url":"https://github.com/odesk/phystrix/issues/19#issuecomment-250774259","issue_url":"https://api.github.com/repos/odesk/phystrix/issues/19","id":250774259,"user":{"login":"lcf","id":185882,"avatar_url":"https://avatars.githubusercontent.com/u/185882?v=3","gravatar_id":"","url":"https://api.github.com/users/lcf","html_url":"https://github.com/lcf","followers_url":"https://api.github.com/users/lcf/followers","following_url":"https://api.github.com/users/lcf/following{/other_user}","gists_url":"https://api.github.com/users/lcf/gists{/gist_id}","starred_url":"https://api.github.com/users/lcf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lcf/subscriptions","organizations_url":"https://api.github.com/users/lcf/orgs","repos_url":"https://api.github.com/users/lcf/repos","events_url":"https://api.github.com/users/lcf/events{/privacy}","received_events_url":"https://api.github.com/users/lcf/received_events","type":"User","site_admin":false},"created_at":"2016-09-30T15:26:19Z","updated_at":"2016-09-30T15:26:19Z","body":"We work with multi-node load-balanced environments almost exclusively, with all nodes protected by Phystrix individually. We have all network calls wrapped into Phystrix, therefore using network calls to support Phystrix itself is not acceptable.\r\n\r\nIf you configure Phystrix to break the circuit when 50% of calls fail - it doesn't really matter if it's one node or many, result will be the same.\r\n\r\nAre there examples when having a redis-like single storage for metrics would be beneficial?"}}
{"actor":{"display_login":"lcf"}}