https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=752 Mihael Hategan <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |WAITING FOR USER INPUT --- Comment #1 from Mihael Hategan <[email protected]> 2014-10-18 18:28:26 --- I'm not entirely sure I understand what is being described here. However, here is my take on what I do understand: 1. worker jobs not being retried is by design. It is the design part that says that any error, even transient, should make its way back to the client, and if the client (swift in this case) wants to re-try a job, it can do so. If the error was transient, a subsequent try will eventually succeed. The point is that, like many other job submission services, coasters is not fault-tolerant. Swift handles that part, and it does not need to be duplicated in coasters. 2. As long as there are more jobs than workers available to run them, the coaster service should try to start more workers. Is this not happening in this case? -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.