{"action":"opened","issue":{"url":"https://api.github.com/repos/NodeRedis/node_redis/issues/875","labels_url":"https://api.github.com/repos/NodeRedis/node_redis/issues/875/labels{/name}","comments_url":"https://api.github.com/repos/NodeRedis/node_redis/issues/875/comments","events_url":"https://api.github.com/repos/NodeRedis/node_redis/issues/875/events","html_url":"https://github.com/NodeRedis/node_redis/issues/875","id":109391619,"number":875,"title":"usage with node cluster causes intermittent latency issues","user":{"login":"torra","id":3345347,"avatar_url":"https://avatars.githubusercontent.com/u/3345347?v=3","gravatar_id":"","url":"https://api.github.com/users/torra","html_url":"https://github.com/torra","followers_url":"https://api.github.com/users/torra/followers","following_url":"https://api.github.com/users/torra/following{/other_user}","gists_url":"https://api.github.com/users/torra/gists{/gist_id}","starred_url":"https://api.github.com/users/torra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/torra/subscriptions","organizations_url":"https://api.github.com/users/torra/orgs","repos_url":"https://api.github.com/users/torra/repos","events_url":"https://api.github.com/users/torra/events{/privacy}","received_events_url":"https://api.github.com/users/torra/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-01T21:45:28Z","updated_at":"2015-10-01T21:45:28Z","closed_at":null,"body":"We run ec2 instances using node cluster, with ~5 workers per instance. We were using an old version (0.10.3), and when we tried to upgrade we started seeing timeouts on the load balancer. Here is what I noticed:\r\n- disabling cluster fixes the issue\r\n- leaving cluster enabled, but only using one worker fixes the issue\r\n- reverting back to 0.10.3 fixes the issue\r\n\r\nUnfortunately I don't have time to dig much deeper, but something since 0.10 seems to not play nice with cluster. Our redis server is running locally, and we connect via unix socket.\r\n\r\nAny thoughts on what would cause such behavior?"}}