{"comment":{"created_at":"2011-10-07T20:01:55Z","body":"@hone Please consider randomizing the interval in some way.  I've had to run a cluster with 15,000 workers and you can end up with a thundering herd problem if you have too much activity hitting redis all at once.  We had to stagger our worker startups, which obviously would affect the interval period, to avoid that issue once already.  But that largely works because the jobs all run with varying execution times.  I'm afraid with the parent processes all basically being spawned at the same time (we use resque-pool for each machine), and then starting up a heartbeat schedule that there will be periods where we just hammer the redis server and effectively DDoS the cluster.","updated_at":"2011-10-07T20:01:55Z","url":"https://api.github.com/repos/defunkt/resque/issues/comments/2327382","id":2327382,"user":{"avatar_url":"https://secure.gravatar.com/avatar/0f2cc1aefa9529ba8627270cf81d2160?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/nirvdrum","id":12584,"login":"nirvdrum"}},"action":"created","issue":{"number":319,"created_at":"2011-06-21T09:51:05Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"Because heroku run's every process in a separated closed environment the `ps` command doesn't list any worker processes.\r\n\r\nWe are currently running in some problems with heroku because they don't gracefully kill workers on deploy or restart.\r\nThis causes old workers to stay \"alive\" in redis. I'm not really sure if either heroku should kill workers gracefully or if resque should look into an other way to check alive workers.\r\nIt might be an idea to let a worker update a timestamp or something in redis once in a while and that resque will cleanup workers which havn't checked in for x seconds/minutes. I would be open to contribute for this issue but would like to discuss things first (maybe there is already a solution or i just do something wrong).","comments":51,"title":"prune_dead_workers doesn't work on heroku cedar","updated_at":"2011-10-07T20:01:55Z","url":"https://api.github.com/repos/defunkt/resque/issues/319","id":1090851,"assignee":null,"milestone":null,"closed_at":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/ee93d361133faa26afbdabbab7b351ba?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/dhiemstra","id":37780,"login":"dhiemstra"},"html_url":"https://github.com/defunkt/resque/issues/319","labels":[],"state":"open"},"legacy":{"issue_id":1090851,"comment_id":2327382}}