Not necessarily to address in this MR, but if these are expensive queries that often timeout, we could perhaps work on directing the reads to a replica, and performing only the drop bit on the primary? Since this is a cronjob, I suspect this won't actually be sensitive to replication lag, would it?
@jreporter, I'm not sure how urgent it is in relation to other priorities, but it does seem like it's a risk to database availability, although the work in the original issue should also help alleviate that. So, yes, I think it would be good to schedule this quickly.
This is kind of blocked on support for idempotent jobs when using :sticky or :delayed but we could also remove the idempotent! designation, for now, just to see how read-only performs.
We could make a follow-up issue to put the idempotent designation back.
@allison.browne@drew Since it's being blocked by that epic, I wonder if we should actually try to get this scheduled following the EA instead, or is it worth doing this part while we wait for that epic?
we could also remove the idempotent! designation, for now, just to see how read-only performs.
Also do you have a severity/priority in mind? I think ~"technical debt" is the right label.
After the Engineering Allocation makes sense to me. Anything that we'd want to do urgently in this milestone would, IMO, fall under #291010 (closed) which is already a part of the EA.
@drew How urgent would you consider this ~"technical debt" to be (e.g. severity labels) - which would help to understand how quickly it needs to be addressed.
@avielle i'm moving this to the backlog until the blocking issue is resolved since it's outside the team unless you think we can pick it up from groupmemory
@jheimbuck_gl I don't think it's a high enough priority to make picking up an issue from another group worth it. I'm okay with having this in %Backlog for now
I'm attaching severity3 to this because I don't think it requires the urgency we bring to severity2, but is a low-risk and conceptually solid idea for reducing workload on the primary, which is an going concern of ours.