On Tue, Jan 12, 2016 at 3:56 PM, Brian Hatfield
wrote:
> Hi,
>
> We currently run a (relatively) small Mesos/Aurora cluster, and don't
> always have significant resource overhead available.
>
> Sometimes, we go to schedule a job and we're just short of what we
>
ters to help verify
>>
>> -Jake
>>
>> On Tue, Jun 14, 2016 at 7:43 PM, John Sirois <jsir...@apache.org> wrote:
>>
>> > I'd like to move forward with
>> > https://issues.apache.org/jira/browse/AURORA-1669 asap; ie: removing
>> > l
te:
>>
>> Wow, thanks a lot John!
>> Will give it a shot and get back to you!
>>
>> On 15 July 2016 at 18:05, John Sirois <john.sir...@gmail.com> wrote:
>>>
>>> Here's a workaround for you to try. If this works, I can modify the
Aurora pants
It may be simplest to start from a known state, though this will be
bandwidth expensive!:
Can you try a `vagrant destroy` on an up to date master and then `vagrant
up` if you haven't already?
On Jul 13, 2016 4:26 AM, "Yiannis Gkoufas" wrote:
> Hi guys,
>
> I was trying
<
>> stephan@blue-yonder.com>
>> wrote:
>>
>> > The curator backend has been working well for us so far. I believe it is
>> > safe to make it the default for the next release, and to drop the old
>> code
>> > in the release after tha
...
>
> ...
>
> Sep 26 18:21:37 machine62 aurora-scheduler[24743]: E0926 18:21:37.205
> [Lifecycle-0, SchedulerLifecycle$4:235] Framework has not been registered
> within the tolerated delay.
>
> On Tue, Sep 26, 2017 at 2:34 PM, John Sirois <john.sir...@gmail.com>
> wro
On Tue, Sep 26, 2017 at 3:31 PM, Mohit Jaggi wrote:
> Actually I wonder if the "register" here is for Aurora to register with
> mesos as a framework...I was assuming it refered to registering with ZK as
> a leader.
>
Bingo.
>
> On Tue, Sep 26, 2017 at 2:27 PM, Renan
MesosCallbackHandler$MesosCallbackHandlerImpl:180]
> Registered with ID value: "4ca9aa06-3214-4d2c-a678-0832e2f84d17-"
>
> On Tue, Sep 26, 2017 at 3:30 PM, John Sirois <john.sir...@gmail.com>
> wrote:
>
>> > ... but it succeeded(see logs at the e