{"action":"opened","issue":{"url":"https://api.github.com/repos/mperham/sidekiq/issues/2945","repository_url":"https://api.github.com/repos/mperham/sidekiq","labels_url":"https://api.github.com/repos/mperham/sidekiq/issues/2945/labels{/name}","comments_url":"https://api.github.com/repos/mperham/sidekiq/issues/2945/comments","events_url":"https://api.github.com/repos/mperham/sidekiq/issues/2945/events","html_url":"https://github.com/mperham/sidekiq/issues/2945","id":150441417,"number":2945,"title":"Question: Global start-stop event","user":{"login":"vnazarenko","id":54346,"avatar_url":"https://avatars.githubusercontent.com/u/54346?v=3","gravatar_id":"","url":"https://api.github.com/users/vnazarenko","html_url":"https://github.com/vnazarenko","followers_url":"https://api.github.com/users/vnazarenko/followers","following_url":"https://api.github.com/users/vnazarenko/following{/other_user}","gists_url":"https://api.github.com/users/vnazarenko/gists{/gist_id}","starred_url":"https://api.github.com/users/vnazarenko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vnazarenko/subscriptions","organizations_url":"https://api.github.com/users/vnazarenko/orgs","repos_url":"https://api.github.com/users/vnazarenko/repos","events_url":"https://api.github.com/users/vnazarenko/events{/privacy}","received_events_url":"https://api.github.com/users/vnazarenko/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-22T18:32:28Z","updated_at":"2016-04-22T18:32:28Z","closed_at":null,"body":"Hi, we are using sidekiq with some long-running jobs. This jobs has ability to shutdown gracefully and resume from stopped place. We have 10 servers with 2 processes on each server, and during deploy all tasks are stopped. So after deployment is finished, we need to run some 'bootstrap' script which will prepare some data and start corresponding tasks. Now I use   config.on(:startup) section in initializer, \r\nbut it works for each started process, and even when last process is not yet stopped, first has been already started. So what is the best way to handle 'one' for all processes on all server callbacks?"}}