Hi Mohit,
I believe you are running into a form of
https://issues.apache.org/jira/browse/AURORA-1596. Assuming it is the same
cause, you might try to increase the lock timeout introduced in the linked
issue.
As a much more viable solution, I would recommend to update to 0.19 though:
Aurora
> Q1: Does Aurora use COMMAND or DEFAULT executor?
Aurora is currently using neither. In Mesos terms Thermos is a CUSTOM executor.
On top, Aurora supports alternative custom executors [1] such as the Docker
compose executor [2].
Mesos seems to be betting on the new DEFAULT executor. It should
Thanks for driving this effort! I am looking forward to the change, as
it hopefully makes it easier for new contributors.
On Tue, 2018-06-19 at 13:21 -0700, Renan DelValle wrote:
> All,
>
> The vote to move from the legacy ASF git hosting to the GitBox service has
> passed. When we finish our
