Hi Isaac, That behaviour is definitely not intentional. This sounds like it was the bug with an incorrect JOIN type in SQL. The ticket tracking that issue is here:
https://issues.apache.org/jira/browse/AURORA-640 I'm not sure though if the fix made it in in time for that release. - David On Wed, Sep 10, 2014 at 11:03 AM, Isaac Councill <is...@hioscar.com> wrote: > Hi, > > I just experienced an issue where a job update was failing and leaving a > lock in place. Expected. What I didn't expect was that while that lock was > in place, it was not possible to interact with any job (old or new) due to > the lock. All the jobs I tested were in the same role and prod environment. > > Is this behavior intentional? > > I'm working with the 0.5.0-incubating release. >
