Reservation status monitoring

[박도형]

Hi Folks,
 
Is there a easy way to see the current overall status of reservation of resources in Mesos Master?
I want to monitor status such as reserved resources per agent or per role with the Mesos Web UI.
 
DH Park.
 
Dohyeong Park, Engineer
Cloud Platform Group, Mobile R Office
Mobile Communication Business
SAMSUNG ELECTRONICS CO,.LTD.
E-mail. doit.p...@samsung.com 
 

Re: java driver/shutdown call

[Mohit Jaggi]

I am trying to change Apache Aurora's code to call SHUTDOWN instead of
KILL. SHUTDOWN seems to offer more robust termination than KILL.

On Tue, Jan 16, 2018 at 6:40 PM, Benjamin Mahler  wrote:

> Mohit, what are you trying to accomplish by going from KILL to SHUTDOWN?
>
> On Tue, Jan 16, 2018 at 5:15 PM, Joseph Wu  wrote:
>
>> If a framework launches tasks, then it will use an executor.  Mesos
>> provides a "default" executor if the framework doesn't explicitly specify
>> an executor.  (And the Shutdown call will work with that default executor.)
>>
>> On Tue, Jan 16, 2018 at 4:49 PM, Mohit Jaggi 
>> wrote:
>>
>>> Gotcha. Another question: if a framework doesn't use executors, can it
>>> still use the SHUTDOWN call?
>>>
>>> On Fri, Jan 12, 2018 at 2:37 PM, Anand Mazumdar <
>>> mazumdar.an...@gmail.com> wrote:
>>>
 Yes; It's a newer interface that still allows you to switch between the
 v1 (new) and the old API.

 -anand

 On Fri, Jan 12, 2018 at 3:28 PM, Mohit Jaggi 
 wrote:

> Are you suggesting
>
> *send(new Call(METHOD, Param1, ...)) *
>
> instead of
>
> *driver.method(Param1, )*
>
> *?*
>
> On Fri, Jan 12, 2018 at 10:59 AM, Anand Mazumdar <
> mazumdar.an...@gmail.com> wrote:
>
>> Mohit,
>>
>> You can use the V1Mesos class that uses the v1 API internally
>> allowing you to send the 'SHUTDOWN' call. We also have a V0Mesos class 
>> that
>> uses the old scheduler driver internally.
>>
>> -anand
>>
>> On Wed, Jan 10, 2018 at 2:53 PM, Mohit Jaggi 
>> wrote:
>>
>>> Thanks Vinod. Is there a V1SchedulerDriver.java file? I see
>>> https://github.com/apache/mesos/tree/72752fc6deb8ebcbfbd
>>> 5448dc599ef3774339d31/src/java/src/org/apache/mesos/v1/scheduler
>>> but it does not have a V1 driver.
>>>
>>> On Fri, Jan 5, 2018 at 3:59 PM, Vinod Kone 
>>> wrote:
>>>
 That's right. It is only available for v1 schedulers.

 On Fri, Jan 5, 2018 at 3:38 PM, Mohit Jaggi 
 wrote:

> Folks,
> I am trying to change Apache Aurora's code to call SHUTDOWN
> instead of KILL. However, it seems that the SchedulerDriver class in 
> Mesos
> does not have a shutdownExecutor() call.
>
> https://github.com/apache/mesos/blob/72752fc6deb8ebcbfbd5448
> dc599ef3774339d31/src/java/src/org/apache/mesos/SchedulerDri
> ver.java
>
> Mohit.
>


>>>
>>
>>
>> --
>> Anand Mazumdar
>>
>
>


 --
 Anand Mazumdar

>>>
>>>
>>
>

Re: Mesos slave ID change after reboot

[Benjamin Mahler]

Yes, the agent used to check for the boot id having changed in order to
decide whether to try to recover.

On Wed, Jan 10, 2018 at 5:53 PM, Srikanth Viswanathan 
wrote:

> I am trying to understand under what cases the mesos slave ID changes in
> response to reboot.  I noticed this note at http://mesos.apache.org/
> documentation/latest/upgrades/#upgrading-from-1-3-x-to-1-4-x:
>
> Agent is now allowed to recover its agent ID post a host reboot. This
>> prevents the unnecessary discarding of agent ID by prior Mesos versions.
>> Notes about backwards compatibility:
>>
>>- In case the agent’s recovery runs into agent info mismatch which
>>may happen due to resource change associated with reboot, it’ll fall back
>>to recovering as a new agent (existing behavior).
>>
>>
>>- In other cases such as checkpointed resources (e.g. persistent
>>volumes) being incompatible with the agent’s resources the recovery will
>>still fail (existing behavior).
>>
>>
> I was wondering if the behavior prior to 1.3 is also similarly
> well-defined. Is the answer "Will always change after a reboot"?
>
> Thanks,
> Srikanth
>

Re: java driver/shutdown call

[Benjamin Mahler]

Mohit, what are you trying to accomplish by going from KILL to SHUTDOWN?

On Tue, Jan 16, 2018 at 5:15 PM, Joseph Wu  wrote:

> If a framework launches tasks, then it will use an executor.  Mesos
> provides a "default" executor if the framework doesn't explicitly specify
> an executor.  (And the Shutdown call will work with that default executor.)
>
> On Tue, Jan 16, 2018 at 4:49 PM, Mohit Jaggi  wrote:
>
>> Gotcha. Another question: if a framework doesn't use executors, can it
>> still use the SHUTDOWN call?
>>
>> On Fri, Jan 12, 2018 at 2:37 PM, Anand Mazumdar > > wrote:
>>
>>> Yes; It's a newer interface that still allows you to switch between the
>>> v1 (new) and the old API.
>>>
>>> -anand
>>>
>>> On Fri, Jan 12, 2018 at 3:28 PM, Mohit Jaggi 
>>> wrote:
>>>
 Are you suggesting

 *send(new Call(METHOD, Param1, ...)) *

 instead of

 *driver.method(Param1, )*

 *?*

 On Fri, Jan 12, 2018 at 10:59 AM, Anand Mazumdar <
 mazumdar.an...@gmail.com> wrote:

> Mohit,
>
> You can use the V1Mesos class that uses the v1 API internally allowing
> you to send the 'SHUTDOWN' call. We also have a V0Mesos class that uses 
> the
> old scheduler driver internally.
>
> -anand
>
> On Wed, Jan 10, 2018 at 2:53 PM, Mohit Jaggi 
> wrote:
>
>> Thanks Vinod. Is there a V1SchedulerDriver.java file? I see
>> https://github.com/apache/mesos/tree/72752fc6deb8ebcbfbd
>> 5448dc599ef3774339d31/src/java/src/org/apache/mesos/v1/scheduler but
>> it does not have a V1 driver.
>>
>> On Fri, Jan 5, 2018 at 3:59 PM, Vinod Kone 
>> wrote:
>>
>>> That's right. It is only available for v1 schedulers.
>>>
>>> On Fri, Jan 5, 2018 at 3:38 PM, Mohit Jaggi 
>>> wrote:
>>>
 Folks,
 I am trying to change Apache Aurora's code to call SHUTDOWN instead
 of KILL. However, it seems that the SchedulerDriver class in Mesos 
 does not
 have a shutdownExecutor() call.

 https://github.com/apache/mesos/blob/72752fc6deb8ebcbfbd5448
 dc599ef3774339d31/src/java/src/org/apache/mesos/SchedulerDri
 ver.java

 Mohit.

>>>
>>>
>>
>
>
> --
> Anand Mazumdar
>


>>>
>>>
>>> --
>>> Anand Mazumdar
>>>
>>
>>
>

Re: java driver/shutdown call

[Joseph Wu]

If a framework launches tasks, then it will use an executor.  Mesos
provides a "default" executor if the framework doesn't explicitly specify
an executor.  (And the Shutdown call will work with that default executor.)

On Tue, Jan 16, 2018 at 4:49 PM, Mohit Jaggi  wrote:

> Gotcha. Another question: if a framework doesn't use executors, can it
> still use the SHUTDOWN call?
>
> On Fri, Jan 12, 2018 at 2:37 PM, Anand Mazumdar 
> wrote:
>
>> Yes; It's a newer interface that still allows you to switch between the
>> v1 (new) and the old API.
>>
>> -anand
>>
>> On Fri, Jan 12, 2018 at 3:28 PM, Mohit Jaggi 
>> wrote:
>>
>>> Are you suggesting
>>>
>>> *send(new Call(METHOD, Param1, ...)) *
>>>
>>> instead of
>>>
>>> *driver.method(Param1, )*
>>>
>>> *?*
>>>
>>> On Fri, Jan 12, 2018 at 10:59 AM, Anand Mazumdar <
>>> mazumdar.an...@gmail.com> wrote:
>>>
 Mohit,

 You can use the V1Mesos class that uses the v1 API internally allowing
 you to send the 'SHUTDOWN' call. We also have a V0Mesos class that uses the
 old scheduler driver internally.

 -anand

 On Wed, Jan 10, 2018 at 2:53 PM, Mohit Jaggi 
 wrote:

> Thanks Vinod. Is there a V1SchedulerDriver.java file? I see
> https://github.com/apache/mesos/tree/72752fc6deb8ebcbfbd
> 5448dc599ef3774339d31/src/java/src/org/apache/mesos/v1/scheduler but
> it does not have a V1 driver.
>
> On Fri, Jan 5, 2018 at 3:59 PM, Vinod Kone 
> wrote:
>
>> That's right. It is only available for v1 schedulers.
>>
>> On Fri, Jan 5, 2018 at 3:38 PM, Mohit Jaggi 
>> wrote:
>>
>>> Folks,
>>> I am trying to change Apache Aurora's code to call SHUTDOWN instead
>>> of KILL. However, it seems that the SchedulerDriver class in Mesos does 
>>> not
>>> have a shutdownExecutor() call.
>>>
>>> https://github.com/apache/mesos/blob/72752fc6deb8ebcbfbd5448
>>> dc599ef3774339d31/src/java/src/org/apache/mesos/SchedulerDriver.java
>>>
>>> Mohit.
>>>
>>
>>
>


 --
 Anand Mazumdar

>>>
>>>
>>
>>
>> --
>> Anand Mazumdar
>>
>
>

Re: java driver/shutdown call

[Mohit Jaggi]

Gotcha. Another question: if a framework doesn't use executors, can it
still use the SHUTDOWN call?

On Fri, Jan 12, 2018 at 2:37 PM, Anand Mazumdar 
wrote:

> Yes; It's a newer interface that still allows you to switch between the v1
> (new) and the old API.
>
> -anand
>
> On Fri, Jan 12, 2018 at 3:28 PM, Mohit Jaggi  wrote:
>
>> Are you suggesting
>>
>> *send(new Call(METHOD, Param1, ...)) *
>>
>> instead of
>>
>> *driver.method(Param1, )*
>>
>> *?*
>>
>> On Fri, Jan 12, 2018 at 10:59 AM, Anand Mazumdar <
>> mazumdar.an...@gmail.com> wrote:
>>
>>> Mohit,
>>>
>>> You can use the V1Mesos class that uses the v1 API internally allowing
>>> you to send the 'SHUTDOWN' call. We also have a V0Mesos class that uses the
>>> old scheduler driver internally.
>>>
>>> -anand
>>>
>>> On Wed, Jan 10, 2018 at 2:53 PM, Mohit Jaggi 
>>> wrote:
>>>
 Thanks Vinod. Is there a V1SchedulerDriver.java file? I see
 https://github.com/apache/mesos/tree/72752fc6deb8ebcbfbd
 5448dc599ef3774339d31/src/java/src/org/apache/mesos/v1/scheduler but
 it does not have a V1 driver.

 On Fri, Jan 5, 2018 at 3:59 PM, Vinod Kone 
 wrote:

> That's right. It is only available for v1 schedulers.
>
> On Fri, Jan 5, 2018 at 3:38 PM, Mohit Jaggi 
> wrote:
>
>> Folks,
>> I am trying to change Apache Aurora's code to call SHUTDOWN instead
>> of KILL. However, it seems that the SchedulerDriver class in Mesos does 
>> not
>> have a shutdownExecutor() call.
>>
>> https://github.com/apache/mesos/blob/72752fc6deb8ebcbfbd5448
>> dc599ef3774339d31/src/java/src/org/apache/mesos/SchedulerDriver.java
>>
>> Mohit.
>>
>
>

>>>
>>>
>>> --
>>> Anand Mazumdar
>>>
>>
>>
>
>
> --
> Anand Mazumdar
>