Process lease requests using a task queue |
|||
Issue descriptionThis will scale much better than a cron worker. If the lease request can be entirely held in the task queue maybe we don't need to store it in datastore any more? Then you won't need to garbage collect requests that couldn't be fulfilled - just let the task fail enough times.
,
Feb 15 2017
Is this PRR-blocking? I was going to consider this as part of a larger MP redesign which I'd prefer to push to a later quarter.
,
Feb 16 2017
http://shortn/_hR7wI9rSiG: the handlers aren't in any danger of hitting the request deadline yet, so this isn't so urgent. Can you keep me in the loop wrt the redesign? The PRR should cover that too.
,
Feb 16 2017
Sure, but I don't want to start on the redesign right now. I'd like to defer this to after the PRR is done. If another PRR is needed for a redesign that's fine, I'll loop you in.
,
Feb 24 2017
Removing PRR-blocker. This is a huge change that will come with a redesign in another quarter.
,
Jul 28
This doesn't make sense. Lease requests are processed asynchronously, and the client needs to be able to get updates on its lease requests, which means something needs to be written to the datastore. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dsansome@chromium.org
, Feb 15 2017