Page MenuHomePhabricator

Make taskmaster consumption of failed tasks more FIFO-ey
ClosedPublic

Authored by epriestley on Dec 9 2013, 4:04 AM.
Tags
None
Referenced Files
F14063348: D7746.diff
Mon, Nov 18, 5:57 PM
F14034084: D7746.diff
Sat, Nov 9, 10:03 PM
F14007056: D7746.diff
Mon, Oct 28, 10:54 PM
F13976433: D7746.id.diff
Oct 18 2024, 2:14 PM
F13963339: D7746.diff
Oct 15 2024, 3:20 PM
Unknown Object (File)
Oct 13 2024, 5:42 AM
Unknown Object (File)
Oct 10 2024, 5:39 AM
Unknown Object (File)
Oct 9 2024, 3:07 PM
Subscribers

Details

Summary

Ref T1049. See discussion in D7745. We have some specific interest in this for D7745, but generally we want to consume tasks with expired leases in roughly FIFO order, just like we consume new tasks in roughly FIFO order. Currently, when we select an expired task we order them by id, but this is the original insert order, not lease expiration order. Instead, order by leaseExpires.

This query is actually much better than the old one was, since the WHERE part is leaseExpries < VALUE.

Test Plan

Ran EXPLAIN on the query. Ran a taskmaster in debug mode and saw it lease new and expired tasks successfully.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

epriestley updated this revision to Unknown Object (????).Dec 9 2013, 4:16 AM
  • Add explicit test coverage. I was thinking this would be a pain to cover, but we actually have good infrastructure here already.