https://bugzilla.wikimedia.org/show_bug.cgi?id=57613
--- Comment #7 from Marc A. Pelletier <[email protected]> --- (In reply to comment #6) > Is there really something wrong with gearman > or jenkins? The fact that neither of them solves the stated problem set? (Well, I suppose Jenkins could be coerced into doing something similar by combining its job monitoring with some manually crafted schedules; but that's sorta like using a car to crack nuts by driving over them -- it'll /work/ but it's hardly the best solution). Also, Jenkins is exactly as much a SPOF just running cron is; in which case it provides no benefit beyond the ability to farm out the actual run. I'm not even sure where you see Gearman as even related. It's a fairly nice distributed RPC-like dispatcher, but still requires a process to schedule and start jobs which leads us back to the initial problem. Neither of those provide any help with the stated objective of "make sure X happens at time T (or interval I)". Chronos gets close to the stated objective but is (a) highly complex to use and (b) has several boatloads of heavy external dependencies. This is not a new problem; and it's still actively discussed. May places have constructed workarounds[2] and ad-hoc systems to do just that[3]; I'm hoping we can make a solution that is applicable to the general case. [1] http://nerds.airbnb.com/introducing-chronos/ [2] http://kvz.io/blog/2012/12/31/lock-your-cronjobs/ [3] http://act.yapc.eu/lpw2012/talk/4291 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
