Does your build contain commit 2b78aff? That was the fix for AURORA-596, which it sounds like what you are referring to. A build with that commit should course-correct your state.
-=Bill On Tue, Aug 5, 2014 at 4:08 PM, Isaac Councill <is...@hioscar.com> wrote: > Hi, > > I noticed this issue after being hit with the "Unique index or primary key > violation" error on one slave machine. Is there a recommended workaround to > reset the db state safely? Currently aurora will not schedule jobs on that > slave. > > Thanks, > Isaac >
