aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko" <>
Subject Review Request 16310: Dropping duplicate LOCK error message.
Date Tue, 17 Dec 2013 02:02:23 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Aurora, Bill Farner and Brian Wickman.

Repository: aurora


Updater prints duplicate LOCK error message in case of held lock.


  src/main/python/twitter/aurora/client/api/ 32bd6a1bf6bf401b0341b6e14e570d83c3e79dd5



Tested via local source distribution:
$ dist/aurora_client.pex update smf1-test/mkhutornenko/test/cron_hello_world aurora/internal/examples/hello_world.aurora

 INFO] Updating job: cron_hello_world
 INFO] Response from scheduler: LOCK_ERROR (message: Operation for: mkhutornenko/test/cron_hello_world
is already in progress. Started at: Tue Dec 17 00:56:43 UTC 2013. Current owner: mkhutornenko.)
Note: if the scheduler detects that a job update is in progress (or was not
properly completed) it will reject subsequent updates.  This is because your
job is likely in a partially-updated state.  You should only begin another
update if you are confident that nobody is updating this job, and that
the job is in a state suitable for an update.

After checking on the above, you may release the update lock on the job by
invoking cancel_update.


Maxim Khutornenko

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message