Permalink
Browse files

readme

  • Loading branch information...
1 parent c1fa019 commit 5955915db3b1f7cc1bde6cfed8c9ac8004a49961 @bvandenbos bvandenbos committed Jul 11, 2012
Showing with 4 additions and 5 deletions.
  1. +4 −5 README.markdown
View
@@ -277,11 +277,10 @@ You may want to have resque-scheduler running on multiple machines for
redudancy. Electing a master and failover is built in and default. Simply
run resque-scheduler on as many machine as you want pointing to the same
redis instance and schedule. The scheduler processes will use redis to
-elect a master process and detect failover when the master dies.
-Precautions are taken to prevent jobs form potentially being queued twice
-during failover even when the clocks of the scheduler machines are slightly
-out of sync (or load effects scheduled job firing time). If you want the
-gory details, look at Resque::SchedulerLocking.
+elect a master process and detect failover when the master dies. Precautions are
+taken to prevent jobs form potentially being queued twice during failover even
+when the clocks of the scheduler machines are slightly out of sync (or load effects
+scheduled job firing time). If you want the gory details, look at Resque::SchedulerLocking.
If the scheduler process(es) goes down for whatever reason, the delayed items
that should have fired during the outage will fire once the scheduler process

0 comments on commit 5955915

Please sign in to comment.