Strict MySQL replication (row-based) error related to not being able to delete missing record from celery_taskmeta. I've been able to skip the slave counter by one to restore replication, but I was trying to diagnose the root cause...
Got task from broker: celery.backend_cleanup[812f6707-887d-4db5-b8ff-423c90ca1209] expires:[2013-02-02 16:00:00.051213] Just wondering if the celery.backend_cleanup might be causing an issue if it's running on both nodes at the same time? I can't verify this, but wanted to check if my cluster was misconfigured... Finally got sqlgrey clustering working the way it should (but not the way I want). That *was* the cause of most replication problems. Thanks, Andrew, >JR -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Colin Kissa Sent: Monday, February 04, 2013 10:49 AM To: Baruwa users list Subject: Re: [Baruwa] Celery Cleanup On 04 Feb 2013, at 5:44 PM, Morgan, Jeffrey R. wrote: > For Baruwa v1.1.2, just a quick question regarding celery related DB cleanup > in a MySQL Master-Master configuration: > > Is there any need to change celerybeat schedules to eliminate conflicts for > DB cleanup-related tasks? If so, where should these settings be modified? I > don't see djcelery tables populated with cront/interval/periodictasks > entries, but I have encountered a couple replication errors possibly related > to celery cleanup... I couldn't located any CELERYBEAT_SCHEDULE definitions > either. What kind of errors are you getting, there shouldn't be any as autoincrement fields should be generated correctly based on your mysql setup. And secondly Baruwa does not yet use scheduled tasks so you shouldn't even have entries in those tables. -- www.baruwa.org _______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056 _______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056
