Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of isaac@hioscar.com designates
 209.85.219.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGRA8uOmLnJBSh4aj1mSRx8bABtQq8EL_XFUd_YM_9v1svm-vA@mail.gmail.com>
References: 
 <CAF9aMoZ2JVF=M26ueOgA9Mt06t7jtZm24bkWh_eyr6+v9-=D5A@mail.gmail.com>
	<CAGRA8uOmLnJBSh4aj1mSRx8bABtQq8EL_XFUd_YM_9v1svm-vA@mail.gmail.com>
Date: Tue, 5 Aug 2014 19:36:50 -0400
Message-ID: 
 <CAF9aMob=t_TEx5HueTt0X038wS2qPJN3rorKPPBaxyc4MUJCag@mail.gmail.com>
Subject: Re: (AURORA-596) SQL constraint violation in DbAttributeStore
From: Isaac Councill <isaac@hioscar.com>
To: dev@aurora.incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7bd6b7e86d03c604ffea548f

--047d7bd6b7e86d03c604ffea548f
Content-Type: text/plain; charset=UTF-8

Thanks for that! I was running 0.5.0-rc1 which doesn't have your fix. Now I
have a great excuse to upgrade to the official release, and better
understanding of how to answer my own similar questions in the future.


On Tue, Aug 5, 2014 at 7:25 PM, Bill Farner <wfarner@apache.org> wrote:

> 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 <isaac@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
> >
>

--047d7bd6b7e86d03c604ffea548f--