On 11/16/2016 05:27 PM, Sean Myers wrote: > On 11/16/2016 05:28 PM, Michael Hrivnak wrote: >> Options: >> - We could set the policy to SET_NULL. When the worker entry gets deleted, >> the task would simply lose its record of which worker it ran on. > > +1 to this. +1
> > Since the worker no longer exists in that scenario, I don't think we lose any > data there, right? A reference to a nonexistent worker is as good as NULL. Do > we need to add a task scrubber to find tasks with NULL workers and make sure > they get reassigned? We could also use SET() here, and pass it a callable that > sets it to an extant worker pk, but at the moment I think I prefer SET_NULL. > > _______________________________________________ > Pulp-dev mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-dev >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
