Re: how to change mesos resources

[haosdent]

Glad to hear you solve your problem and share your use case! You are always
welcome.
On Apr 10, 2016 7:48 PM, "Stefano Bianchi"  wrote:

> YS haosdent!
> that exactly works! And is exactly what i mean!!! Thank you a lot, thank
> you all, and sorry if i asked you so many times.
>
> Maybe is better if i present myself to you.
>
> My name is Stefano Bianchi, Italian student of Telecommunication
> engineering, i'm currently doing my master thesis at INFN European Nuclear
> physics institute in Bologna city. I'm working on Tier 1 CNAF
> infrastructure where the cloud infrastructure is based on an Openstack IaaS.
> Here i have run 6 virtual machines 3 masters, for high availability, and 3
> slaves, on one slave i'm running mesos DNS.
> the final goal should be the implementation of a PaaS for science European
> community which allows the exploitation of distributed datacenter resources
> for some computations or experiments. For this purpose i have to integrate
> projcect calico plugin in on mesos, in roder to distribute the tasks among
> different network in a transparent way.
>
> I'm describing my master thesis since i saw that many of you are
> Professors and engineers, so you could have interest on that.
>
> Thanks a lot, probbly in the next few months i will come to write here,
> for the moment i really appreciate your help.
> Thanks again!
>
>
> 2016-04-10 5:12 GMT+02:00 haosdent :
>
>> Good to see you solve the chronos problem. For your current problem, you
>> could edit the /etc/default/mesos-slave file and append the configuration
>> to it
>>
>> ```
>> MESOS_MASTER=131.154.96.32:5050
>> MESOS_HOSTNAME=131.154.96.52
>> MESOS_RESOURCES='cpu(*):1;mem(*):1300;disk(*):9000'
>> MESOS_LOG_DIR=/var/log/mesos
>> ```
>>
>> Then service mesos-slave restart
>>
>> On Sun, Apr 10, 2016 at 8:32 AM, Stefano Bianchi 
>> wrote:
>>
>>> Ops,i did not hide the IP addresses, sorry please don't hack :P
>>>
>>> 2016-04-10 2:30 GMT+02:00 Stefano Bianchi :
>>>
 i solved the chronos problem creating a hostname file in /etc/chronos
 specifying the floating IP inside it.
 Now all is working with changed resources, the only one problem that
 persist is that after launching the command:

 mesos-slave --master=131.154.96.32:5050 --hostname=131.154.96.52
 --resources='cpu(*):1;mem(*):1300;disk(*):9000' --log_dir=/var/log/mesos

 i still have some messages in command line and i cannot use the command
 line.

 You're right haosdent i want run mesos-slave as service, but to do that
 i shoulf press ctrl+c to be able to use the command line, then i commonly
 use: service mesos-slave start command, but running it i obtain that the
 slave registers to the master allocating the default resources.
 How can i fix the changes of resources and run mesos-slave with service
 command?

 Thanks again!

 2016-04-09 22:14 GMT+02:00 Stefano Bianchi :

> Im sorry, the command was just:
>
> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>
> Where i specify the hostname with the floating IP.
>
> Without
> rm -f /tmp/mesos/meta/slaves/latest
> Actually i dont know what this command means...even if i have run it
> before.
> Il 09/apr/2016 20:51, "haosdent"  ha scritto:
>
>> Yes, remove /tmp/mesos/meta/slaves/latest could cause this.
>>
>> On Sun, Apr 10, 2016 at 2:47 AM, Stefano Bianchi <
>> jazzist...@gmail.com> wrote:
>>
>>> Sorry maybe i was not clear.
>>> After that error with chronos i stopped the mesos slave and
>>> restarted it witj service mesos-slave start, and in this way chronos 
>>> job is
>>> working.
>>> Of i stop the slavr and start it again with the command that changes
>>> the resources i get the error.
>>> In both cases i see in framework tab of mesos, that the hostname
>>> related to chronos is non resolvable "mesos2.novalocal"
>>> Im asking to my self if this can cause problem with this comamand:
>>>
>>> rm -f /tmp/mesos/meta/slaves/latest
>>>
>>>
>>> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
>>> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>>> Il 09/apr/2016 19:28, "haosdent"  ha scritto:
>>>
>>> >No it does not happen normally, that message comes out only after
>>> i launched the command to change the reaources. Maybe i should create, 
>>> as i
>>> made both for mesos and marathon, the hostname file for Chronos in 
>>> /etc/chronos
>>> and put it inside the public IP resolvable?
>>>
>>> Sorry could not get your points here. What happens if you create a
>>> new chronos job and launch it? Is it still error?
>>>

Re: how to change mesos resources

[Stefano Bianchi]

YS haosdent!
that exactly works! And is exactly what i mean!!! Thank you a lot, thank
you all, and sorry if i asked you so many times.

Maybe is better if i present myself to you.

My name is Stefano Bianchi, Italian student of Telecommunication
engineering, i'm currently doing my master thesis at INFN European Nuclear
physics institute in Bologna city. I'm working on Tier 1 CNAF
infrastructure where the cloud infrastructure is based on an Openstack IaaS.
Here i have run 6 virtual machines 3 masters, for high availability, and 3
slaves, on one slave i'm running mesos DNS.
the final goal should be the implementation of a PaaS for science European
community which allows the exploitation of distributed datacenter resources
for some computations or experiments. For this purpose i have to integrate
projcect calico plugin in on mesos, in roder to distribute the tasks among
different network in a transparent way.

I'm describing my master thesis since i saw that many of you are Professors
and engineers, so you could have interest on that.

Thanks a lot, probbly in the next few months i will come to write here, for
the moment i really appreciate your help.
Thanks again!


2016-04-10 5:12 GMT+02:00 haosdent :

> Good to see you solve the chronos problem. For your current problem, you
> could edit the /etc/default/mesos-slave file and append the configuration
> to it
>
> ```
> MESOS_MASTER=131.154.96.32:5050
> MESOS_HOSTNAME=131.154.96.52
> MESOS_RESOURCES='cpu(*):1;mem(*):1300;disk(*):9000'
> MESOS_LOG_DIR=/var/log/mesos
> ```
>
> Then service mesos-slave restart
>
> On Sun, Apr 10, 2016 at 8:32 AM, Stefano Bianchi 
> wrote:
>
>> Ops,i did not hide the IP addresses, sorry please don't hack :P
>>
>> 2016-04-10 2:30 GMT+02:00 Stefano Bianchi :
>>
>>> i solved the chronos problem creating a hostname file in /etc/chronos
>>> specifying the floating IP inside it.
>>> Now all is working with changed resources, the only one problem that
>>> persist is that after launching the command:
>>>
>>> mesos-slave --master=131.154.96.32:5050 --hostname=131.154.96.52
>>> --resources='cpu(*):1;mem(*):1300;disk(*):9000' --log_dir=/var/log/mesos
>>>
>>> i still have some messages in command line and i cannot use the command
>>> line.
>>>
>>> You're right haosdent i want run mesos-slave as service, but to do that
>>> i shoulf press ctrl+c to be able to use the command line, then i commonly
>>> use: service mesos-slave start command, but running it i obtain that the
>>> slave registers to the master allocating the default resources.
>>> How can i fix the changes of resources and run mesos-slave with service
>>> command?
>>>
>>> Thanks again!
>>>
>>> 2016-04-09 22:14 GMT+02:00 Stefano Bianchi :
>>>
 Im sorry, the command was just:

 mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
 --resources='cpu(*):1;mem(*):1000;disk(*):8000'

 Where i specify the hostname with the floating IP.

 Without
 rm -f /tmp/mesos/meta/slaves/latest
 Actually i dont know what this command means...even if i have run it
 before.
 Il 09/apr/2016 20:51, "haosdent"  ha scritto:

> Yes, remove /tmp/mesos/meta/slaves/latest could cause this.
>
> On Sun, Apr 10, 2016 at 2:47 AM, Stefano Bianchi  > wrote:
>
>> Sorry maybe i was not clear.
>> After that error with chronos i stopped the mesos slave and restarted
>> it witj service mesos-slave start, and in this way chronos job is 
>> working.
>> Of i stop the slavr and start it again with the command that changes
>> the resources i get the error.
>> In both cases i see in framework tab of mesos, that the hostname
>> related to chronos is non resolvable "mesos2.novalocal"
>> Im asking to my self if this can cause problem with this comamand:
>>
>> rm -f /tmp/mesos/meta/slaves/latest
>>
>>
>> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
>> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>> Il 09/apr/2016 19:28, "haosdent"  ha scritto:
>>
>> >No it does not happen normally, that message comes out only after i
>> launched the command to change the reaources. Maybe i should create, as i
>> made both for mesos and marathon, the hostname file for Chronos in 
>> /etc/chronos
>> and put it inside the public IP resolvable?
>>
>> Sorry could not get your points here. What happens if you create a
>> new chronos job and launch it? Is it still error?
>>
>> On Sun, Apr 10, 2016 at 1:03 AM, Stefano Bianchi <
>> jazzist...@gmail.com> wrote:
>>
>>>
>>> "I think maybe you clear your work_dir in agent. So those messages
>>> disappear now. Does this always happen when you create a new chronos 
>>> job?"
>>>
>>> No it does not happen 

Re: how to change mesos resources

[haosdent]

Good to see you solve the chronos problem. For your current problem, you
could edit the /etc/default/mesos-slave file and append the configuration
to it

```
MESOS_MASTER=131.154.96.32:5050
MESOS_HOSTNAME=131.154.96.52
MESOS_RESOURCES='cpu(*):1;mem(*):1300;disk(*):9000'
MESOS_LOG_DIR=/var/log/mesos
```

Then service mesos-slave restart

On Sun, Apr 10, 2016 at 8:32 AM, Stefano Bianchi 
wrote:

> Ops,i did not hide the IP addresses, sorry please don't hack :P
>
> 2016-04-10 2:30 GMT+02:00 Stefano Bianchi :
>
>> i solved the chronos problem creating a hostname file in /etc/chronos
>> specifying the floating IP inside it.
>> Now all is working with changed resources, the only one problem that
>> persist is that after launching the command:
>>
>> mesos-slave --master=131.154.96.32:5050 --hostname=131.154.96.52
>> --resources='cpu(*):1;mem(*):1300;disk(*):9000' --log_dir=/var/log/mesos
>>
>> i still have some messages in command line and i cannot use the command
>> line.
>>
>> You're right haosdent i want run mesos-slave as service, but to do that i
>> shoulf press ctrl+c to be able to use the command line, then i commonly
>> use: service mesos-slave start command, but running it i obtain that the
>> slave registers to the master allocating the default resources.
>> How can i fix the changes of resources and run mesos-slave with service
>> command?
>>
>> Thanks again!
>>
>> 2016-04-09 22:14 GMT+02:00 Stefano Bianchi :
>>
>>> Im sorry, the command was just:
>>>
>>> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
>>> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>>>
>>> Where i specify the hostname with the floating IP.
>>>
>>> Without
>>> rm -f /tmp/mesos/meta/slaves/latest
>>> Actually i dont know what this command means...even if i have run it
>>> before.
>>> Il 09/apr/2016 20:51, "haosdent"  ha scritto:
>>>
 Yes, remove /tmp/mesos/meta/slaves/latest could cause this.

 On Sun, Apr 10, 2016 at 2:47 AM, Stefano Bianchi 
 wrote:

> Sorry maybe i was not clear.
> After that error with chronos i stopped the mesos slave and restarted
> it witj service mesos-slave start, and in this way chronos job is working.
> Of i stop the slavr and start it again with the command that changes
> the resources i get the error.
> In both cases i see in framework tab of mesos, that the hostname
> related to chronos is non resolvable "mesos2.novalocal"
> Im asking to my self if this can cause problem with this comamand:
>
> rm -f /tmp/mesos/meta/slaves/latest
>
>
> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
> Il 09/apr/2016 19:28, "haosdent"  ha scritto:
>
> >No it does not happen normally, that message comes out only after i
> launched the command to change the reaources. Maybe i should create, as i
> made both for mesos and marathon, the hostname file for Chronos in 
> /etc/chronos
> and put it inside the public IP resolvable?
>
> Sorry could not get your points here. What happens if you create a new
> chronos job and launch it? Is it still error?
>
> On Sun, Apr 10, 2016 at 1:03 AM, Stefano Bianchi  > wrote:
>
>>
>> "I think maybe you clear your work_dir in agent. So those messages
>> disappear now. Does this always happen when you create a new chronos 
>> job?"
>>
>> No it does not happen normally, that message comes out only after i
>> launched the command to change the reaources. Maybe i should create, as i
>> made both for mesos and marathon, the hostname file for Chronos in
>> /etc/chronos and put it inside the public IP resolvable ?
>>
>> Il 09/apr/2016 18:29, "haosdent"  ha scritto:
>> >
>> > >Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does
>> not exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
>> >
>> > I think maybe you clear your work_dir in agent. So those messages
>> disappear now. Does this always happen when you create a new chronos job?
>> >
>> > > However i tried to launch your command but i still unable to use
>> the terminal after that :P, this is another and minor issue.
>> >
>> > I suppose you want to make mesos agent become a systemclt service.
>> If you use `apt/yum` install mesos from mesosphere, it should OK when you
>> use  `systemctl` to start mesos agent. If you install it from source 
>> code,
>> I think you need take some works to write systemctl service files for 
>> mesos.
>> >
>> > On Sun, Apr 10, 2016 at 12:21 AM, Stefano Bianchi <
>> jazzist...@gmail.com> wrote:
>>
>> >>
>>
>> >> i checked in framework, and i see that in 

Re: how to change mesos resources

[Stefano Bianchi]

Ops,i did not hide the IP addresses, sorry please don't hack :P

2016-04-10 2:30 GMT+02:00 Stefano Bianchi :

> i solved the chronos problem creating a hostname file in /etc/chronos
> specifying the floating IP inside it.
> Now all is working with changed resources, the only one problem that
> persist is that after launching the command:
>
> mesos-slave --master=131.154.96.32:5050 --hostname=131.154.96.52
> --resources='cpu(*):1;mem(*):1300;disk(*):9000' --log_dir=/var/log/mesos
>
> i still have some messages in command line and i cannot use the command
> line.
>
> You're right haosdent i want run mesos-slave as service, but to do that i
> shoulf press ctrl+c to be able to use the command line, then i commonly
> use: service mesos-slave start command, but running it i obtain that the
> slave registers to the master allocating the default resources.
> How can i fix the changes of resources and run mesos-slave with service
> command?
>
> Thanks again!
>
> 2016-04-09 22:14 GMT+02:00 Stefano Bianchi :
>
>> Im sorry, the command was just:
>>
>> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
>> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>>
>> Where i specify the hostname with the floating IP.
>>
>> Without
>> rm -f /tmp/mesos/meta/slaves/latest
>> Actually i dont know what this command means...even if i have run it
>> before.
>> Il 09/apr/2016 20:51, "haosdent"  ha scritto:
>>
>>> Yes, remove /tmp/mesos/meta/slaves/latest could cause this.
>>>
>>> On Sun, Apr 10, 2016 at 2:47 AM, Stefano Bianchi 
>>> wrote:
>>>
 Sorry maybe i was not clear.
 After that error with chronos i stopped the mesos slave and restarted
 it witj service mesos-slave start, and in this way chronos job is working.
 Of i stop the slavr and start it again with the command that changes
 the resources i get the error.
 In both cases i see in framework tab of mesos, that the hostname
 related to chronos is non resolvable "mesos2.novalocal"
 Im asking to my self if this can cause problem with this comamand:

 rm -f /tmp/mesos/meta/slaves/latest


 mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
 --resources='cpu(*):1;mem(*):1000;disk(*):8000'
 Il 09/apr/2016 19:28, "haosdent"  ha scritto:

 >No it does not happen normally, that message comes out only after i
 launched the command to change the reaources. Maybe i should create, as i
 made both for mesos and marathon, the hostname file for Chronos in 
 /etc/chronos
 and put it inside the public IP resolvable?

 Sorry could not get your points here. What happens if you create a new
 chronos job and launch it? Is it still error?

 On Sun, Apr 10, 2016 at 1:03 AM, Stefano Bianchi 
 wrote:

>
> "I think maybe you clear your work_dir in agent. So those messages
> disappear now. Does this always happen when you create a new chronos job?"
>
> No it does not happen normally, that message comes out only after i
> launched the command to change the reaources. Maybe i should create, as i
> made both for mesos and marathon, the hostname file for Chronos in
> /etc/chronos and put it inside the public IP resolvable ?
>
> Il 09/apr/2016 18:29, "haosdent"  ha scritto:
> >
> > >Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does
> not exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
> >
> > I think maybe you clear your work_dir in agent. So those messages
> disappear now. Does this always happen when you create a new chronos job?
> >
> > > However i tried to launch your command but i still unable to use
> the terminal after that :P, this is another and minor issue.
> >
> > I suppose you want to make mesos agent become a systemclt service.
> If you use `apt/yum` install mesos from mesosphere, it should OK when you
> use  `systemctl` to start mesos agent. If you install it from source code,
> I think you need take some works to write systemctl service files for 
> mesos.
> >
> > On Sun, Apr 10, 2016 at 12:21 AM, Stefano Bianchi <
> jazzist...@gmail.com> wrote:
>
> >>
>
> >> i checked in framework, and i see that in correspondence of chronos
> host tab there is a non resolvable hostname... Why?
> >>
> >> 2016-04-09 18:14 GMT+02:00 Stefano Bianchi :
>
> >>>
>
> >>> Thanks haosdent.
> >>> However i tried to see launch that command and what i see is:
> >>> 1) Resources are increased, this is what i expected, good;
> >>> 2) A Chronos Job that run each 2 minutes, is allocated and then
> "Staged";
> >>> is i click on sandbox i obtain this message:
> >>>
> >>> Framework with ID 

Re: how to change mesos resources

[Stefano Bianchi]

i solved the chronos problem creating a hostname file in /etc/chronos
specifying the floating IP inside it.
Now all is working with changed resources, the only one problem that
persist is that after launching the command:

mesos-slave --master=131.154.96.32:5050 --hostname=131.154.96.52
--resources='cpu(*):1;mem(*):1300;disk(*):9000' --log_dir=/var/log/mesos

i still have some messages in command line and i cannot use the command
line.

You're right haosdent i want run mesos-slave as service, but to do that i
shoulf press ctrl+c to be able to use the command line, then i commonly
use: service mesos-slave start command, but running it i obtain that the
slave registers to the master allocating the default resources.
How can i fix the changes of resources and run mesos-slave with service
command?

Thanks again!

2016-04-09 22:14 GMT+02:00 Stefano Bianchi :

> Im sorry, the command was just:
>
> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>
> Where i specify the hostname with the floating IP.
>
> Without
> rm -f /tmp/mesos/meta/slaves/latest
> Actually i dont know what this command means...even if i have run it
> before.
> Il 09/apr/2016 20:51, "haosdent"  ha scritto:
>
>> Yes, remove /tmp/mesos/meta/slaves/latest could cause this.
>>
>> On Sun, Apr 10, 2016 at 2:47 AM, Stefano Bianchi 
>> wrote:
>>
>>> Sorry maybe i was not clear.
>>> After that error with chronos i stopped the mesos slave and restarted it
>>> witj service mesos-slave start, and in this way chronos job is working.
>>> Of i stop the slavr and start it again with the command that changes the
>>> resources i get the error.
>>> In both cases i see in framework tab of mesos, that the hostname related
>>> to chronos is non resolvable "mesos2.novalocal"
>>> Im asking to my self if this can cause problem with this comamand:
>>>
>>> rm -f /tmp/mesos/meta/slaves/latest
>>>
>>>
>>> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
>>> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>>> Il 09/apr/2016 19:28, "haosdent"  ha scritto:
>>>
>>> >No it does not happen normally, that message comes out only after i
>>> launched the command to change the reaources. Maybe i should create, as i
>>> made both for mesos and marathon, the hostname file for Chronos in 
>>> /etc/chronos
>>> and put it inside the public IP resolvable?
>>>
>>> Sorry could not get your points here. What happens if you create a new
>>> chronos job and launch it? Is it still error?
>>>
>>> On Sun, Apr 10, 2016 at 1:03 AM, Stefano Bianchi 
>>> wrote:
>>>

 "I think maybe you clear your work_dir in agent. So those messages
 disappear now. Does this always happen when you create a new chronos job?"

 No it does not happen normally, that message comes out only after i
 launched the command to change the reaources. Maybe i should create, as i
 made both for mesos and marathon, the hostname file for Chronos in
 /etc/chronos and put it inside the public IP resolvable ?

 Il 09/apr/2016 18:29, "haosdent"  ha scritto:
 >
 > >Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does
 not exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
 >
 > I think maybe you clear your work_dir in agent. So those messages
 disappear now. Does this always happen when you create a new chronos job?
 >
 > > However i tried to launch your command but i still unable to use
 the terminal after that :P, this is another and minor issue.
 >
 > I suppose you want to make mesos agent become a systemclt service. If
 you use `apt/yum` install mesos from mesosphere, it should OK when you use
  `systemctl` to start mesos agent. If you install it from source code, I
 think you need take some works to write systemctl service files for mesos.
 >
 > On Sun, Apr 10, 2016 at 12:21 AM, Stefano Bianchi <
 jazzist...@gmail.com> wrote:

 >>

 >> i checked in framework, and i see that in correspondence of chronos
 host tab there is a non resolvable hostname... Why?
 >>
 >> 2016-04-09 18:14 GMT+02:00 Stefano Bianchi :

 >>>

 >>> Thanks haosdent.
 >>> However i tried to see launch that command and what i see is:
 >>> 1) Resources are increased, this is what i expected, good;
 >>> 2) A Chronos Job that run each 2 minutes, is allocated and then
 "Staged";
 >>> is i click on sandbox i obtain this message:
 >>>
 >>> Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does
 not exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
 >>>
 >>> What does it means? How can i solve it?
 >>> However i tried to launch your command but i still unable to use
 the terminal 

Re: how to change mesos resources

[Stefano Bianchi]

Im sorry, the command was just:

mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
--resources='cpu(*):1;mem(*):1000;disk(*):8000'

Where i specify the hostname with the floating IP.

Without
rm -f /tmp/mesos/meta/slaves/latest
Actually i dont know what this command means...even if i have run it before.
Il 09/apr/2016 20:51, "haosdent"  ha scritto:

> Yes, remove /tmp/mesos/meta/slaves/latest could cause this.
>
> On Sun, Apr 10, 2016 at 2:47 AM, Stefano Bianchi 
> wrote:
>
>> Sorry maybe i was not clear.
>> After that error with chronos i stopped the mesos slave and restarted it
>> witj service mesos-slave start, and in this way chronos job is working.
>> Of i stop the slavr and start it again with the command that changes the
>> resources i get the error.
>> In both cases i see in framework tab of mesos, that the hostname related
>> to chronos is non resolvable "mesos2.novalocal"
>> Im asking to my self if this can cause problem with this comamand:
>>
>> rm -f /tmp/mesos/meta/slaves/latest
>>
>>
>> mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
>> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>> Il 09/apr/2016 19:28, "haosdent"  ha scritto:
>>
>> >No it does not happen normally, that message comes out only after i
>> launched the command to change the reaources. Maybe i should create, as i
>> made both for mesos and marathon, the hostname file for Chronos in 
>> /etc/chronos
>> and put it inside the public IP resolvable?
>>
>> Sorry could not get your points here. What happens if you create a new
>> chronos job and launch it? Is it still error?
>>
>> On Sun, Apr 10, 2016 at 1:03 AM, Stefano Bianchi 
>> wrote:
>>
>>>
>>> "I think maybe you clear your work_dir in agent. So those messages
>>> disappear now. Does this always happen when you create a new chronos job?"
>>>
>>> No it does not happen normally, that message comes out only after i
>>> launched the command to change the reaources. Maybe i should create, as i
>>> made both for mesos and marathon, the hostname file for Chronos in
>>> /etc/chronos and put it inside the public IP resolvable ?
>>>
>>> Il 09/apr/2016 18:29, "haosdent"  ha scritto:
>>> >
>>> > >Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does
>>> not exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
>>> >
>>> > I think maybe you clear your work_dir in agent. So those messages
>>> disappear now. Does this always happen when you create a new chronos job?
>>> >
>>> > > However i tried to launch your command but i still unable to use the
>>> terminal after that :P, this is another and minor issue.
>>> >
>>> > I suppose you want to make mesos agent become a systemclt service. If
>>> you use `apt/yum` install mesos from mesosphere, it should OK when you use
>>>  `systemctl` to start mesos agent. If you install it from source code, I
>>> think you need take some works to write systemctl service files for mesos.
>>> >
>>> > On Sun, Apr 10, 2016 at 12:21 AM, Stefano Bianchi <
>>> jazzist...@gmail.com> wrote:
>>>
>>> >>
>>>
>>> >> i checked in framework, and i see that in correspondence of chronos
>>> host tab there is a non resolvable hostname... Why?
>>> >>
>>> >> 2016-04-09 18:14 GMT+02:00 Stefano Bianchi :
>>>
>>> >>>
>>>
>>> >>> Thanks haosdent.
>>> >>> However i tried to see launch that command and what i see is:
>>> >>> 1) Resources are increased, this is what i expected, good;
>>> >>> 2) A Chronos Job that run each 2 minutes, is allocated and then
>>> "Staged";
>>> >>> is i click on sandbox i obtain this message:
>>> >>>
>>> >>> Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does
>>> not exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
>>> >>>
>>> >>> What does it means? How can i solve it?
>>> >>> However i tried to launch your command but i still unable to use the
>>> terminal after that :P, this is another and minor issue.
>>> >>>
>>> >>>
>>> >>> 2016-04-09 17:34 GMT+02:00 haosdent :
>>>
>>> 
>>>
>>>  Hi, @Stefano You could specify the flag --log_dir when you start
>>> Mesos Agent. For example:
>>> 
>>>  mesos-slave --master=MASTER_ADDRESS:5050
>>> --hostname=slave_public_IP_i_set
>>> --resources='cpu(*):1;mem(*):1000;disk(*):8000' --log_dir=/var/log/mesos
>>> 
>>>  So it would log to files under /var/log/mesos instead of console.
>>> 
>>>  On Sat, Apr 9, 2016 at 10:08 PM, Stefano Bianchi <
>>> jazzist...@gmail.com> wrote:
>>>
>>> >
>>>
>>> > Hi
>>> > All is working fine!
>>> > I can see more disk space and more RAM!
>>> > The only thing that is different is that with the Arjun last
>>> command, i obtain a verbose output, i mean a lot of messages continuously
>>> shown, on command line. i would like to hide them and continue to use the
>>> command line, is it possible?
>>> >
>>> 

Re: how to change mesos resources

[Stefano Bianchi]

Sorry maybe i was not clear.
After that error with chronos i stopped the mesos slave and restarted it
witj service mesos-slave start, and in this way chronos job is working.
Of i stop the slavr and start it again with the command that changes the
resources i get the error.
In both cases i see in framework tab of mesos, that the hostname related to
chronos is non resolvable "mesos2.novalocal"
Im asking to my self if this can cause problem with this comamand:

rm -f /tmp/mesos/meta/slaves/latest


mesos-slave --master=131.154.xxx.xxx:5050 --hostname=131.154.xxx.xxx
--resources='cpu(*):1;mem(*):1000;disk(*):8000'
Il 09/apr/2016 19:28, "haosdent"  ha scritto:

>No it does not happen normally, that message comes out only after i
launched the command to change the reaources. Maybe i should create, as i
made both for mesos and marathon, the hostname file for Chronos in /etc/chronos
and put it inside the public IP resolvable?

Sorry could not get your points here. What happens if you create a new
chronos job and launch it? Is it still error?

On Sun, Apr 10, 2016 at 1:03 AM, Stefano Bianchi 
wrote:

>
> "I think maybe you clear your work_dir in agent. So those messages
> disappear now. Does this always happen when you create a new chronos job?"
>
> No it does not happen normally, that message comes out only after i
> launched the command to change the reaources. Maybe i should create, as i
> made both for mesos and marathon, the hostname file for Chronos in
> /etc/chronos and put it inside the public IP resolvable ?
>
> Il 09/apr/2016 18:29, "haosdent"  ha scritto:
> >
> > >Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
> exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
> >
> > I think maybe you clear your work_dir in agent. So those messages
> disappear now. Does this always happen when you create a new chronos job?
> >
> > > However i tried to launch your command but i still unable to use the
> terminal after that :P, this is another and minor issue.
> >
> > I suppose you want to make mesos agent become a systemclt service. If
> you use `apt/yum` install mesos from mesosphere, it should OK when you use
>  `systemctl` to start mesos agent. If you install it from source code, I
> think you need take some works to write systemctl service files for mesos.
> >
> > On Sun, Apr 10, 2016 at 12:21 AM, Stefano Bianchi 
> wrote:
>
> >>
>
> >> i checked in framework, and i see that in correspondence of chronos
> host tab there is a non resolvable hostname... Why?
> >>
> >> 2016-04-09 18:14 GMT+02:00 Stefano Bianchi :
>
> >>>
>
> >>> Thanks haosdent.
> >>> However i tried to see launch that command and what i see is:
> >>> 1) Resources are increased, this is what i expected, good;
> >>> 2) A Chronos Job that run each 2 minutes, is allocated and then
> "Staged";
> >>> is i click on sandbox i obtain this message:
> >>>
> >>> Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
> exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
> >>>
> >>> What does it means? How can i solve it?
> >>> However i tried to launch your command but i still unable to use the
> terminal after that :P, this is another and minor issue.
> >>>
> >>>
> >>> 2016-04-09 17:34 GMT+02:00 haosdent :
>
> 
>
>  Hi, @Stefano You could specify the flag --log_dir when you start
> Mesos Agent. For example:
> 
>  mesos-slave --master=MASTER_ADDRESS:5050
> --hostname=slave_public_IP_i_set
> --resources='cpu(*):1;mem(*):1000;disk(*):8000' --log_dir=/var/log/mesos
> 
>  So it would log to files under /var/log/mesos instead of console.
> 
>  On Sat, Apr 9, 2016 at 10:08 PM, Stefano Bianchi <
> jazzist...@gmail.com> wrote:
>
> >
>
> > Hi
> > All is working fine!
> > I can see more disk space and more RAM!
> > The only thing that is different is that with the Arjun last
> command, i obtain a verbose output, i mean a lot of messages continuously
> shown, on command line. i would like to hide them and continue to use the
> command line, is it possible?
> >
> > Thanks again!
> 
> 
> 
> 
>  --
>  Best Regards,
>  Haosdent Huang
> >>>
> >>>
> >>
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
>



-- 
Best Regards,
Haosdent Huang

Re: how to change mesos resources

[Stefano Bianchi]

"I think maybe you clear your work_dir in agent. So those messages
disappear now. Does this always happen when you create a new chronos job?"

No it does not happen normally, that message comes out only after i
launched the command to change the reaources. Maybe i should create, as i
made both for mesos and marathon, the hostname file for Chronos in
/etc/chronos and put it inside the public IP resolvable ?

Il 09/apr/2016 18:29, "haosdent"  ha scritto:
>
> >Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
>
> I think maybe you clear your work_dir in agent. So those messages
disappear now. Does this always happen when you create a new chronos job?
>
> > However i tried to launch your command but i still unable to use the
terminal after that :P, this is another and minor issue.
>
> I suppose you want to make mesos agent become a systemclt service. If you
use `apt/yum` install mesos from mesosphere, it should OK when you use
 `systemctl` to start mesos agent. If you install it from source code, I
think you need take some works to write systemctl service files for mesos.
>
> On Sun, Apr 10, 2016 at 12:21 AM, Stefano Bianchi 
wrote:

>>

>> i checked in framework, and i see that in correspondence of chronos host
tab there is a non resolvable hostname... Why?
>>
>> 2016-04-09 18:14 GMT+02:00 Stefano Bianchi :

>>>

>>> Thanks haosdent.
>>> However i tried to see launch that command and what i see is:
>>> 1) Resources are increased, this is what i expected, good;
>>> 2) A Chronos Job that run each 2 minutes, is allocated and then
"Staged";
>>> is i click on sandbox i obtain this message:
>>>
>>> Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
>>>
>>> What does it means? How can i solve it?
>>> However i tried to launch your command but i still unable to use the
terminal after that :P, this is another and minor issue.
>>>
>>>
>>> 2016-04-09 17:34 GMT+02:00 haosdent :



 Hi, @Stefano You could specify the flag --log_dir when you start Mesos
Agent. For example:

 mesos-slave --master=MASTER_ADDRESS:5050
--hostname=slave_public_IP_i_set
--resources='cpu(*):1;mem(*):1000;disk(*):8000' --log_dir=/var/log/mesos

 So it would log to files under /var/log/mesos instead of console.

 On Sat, Apr 9, 2016 at 10:08 PM, Stefano Bianchi 
wrote:

>

> Hi
> All is working fine!
> I can see more disk space and more RAM!
> The only thing that is different is that with the Arjun last command,
i obtain a verbose output, i mean a lot of messages continuously shown, on
command line. i would like to hide them and continue to use the command
line, is it possible?
>
> Thanks again!




 --
 Best Regards,
 Haosdent Huang
>>>
>>>
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang

Re: how to change mesos resources

[haosdent]

>Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.

I think maybe you clear your work_dir in agent. So those messages disappear
now. Does this always happen when you create a new chronos job?

> However i tried to launch your command but i still unable to use the
terminal after that :P, this is another and minor issue.

I suppose you want to make mesos agent become a systemclt service. If you
use `apt/yum` install mesos from mesosphere, it should OK when you use
 `systemctl` to start mesos agent. If you install it from source code, I
think you need take some works to write systemctl service files for mesos.

On Sun, Apr 10, 2016 at 12:21 AM, Stefano Bianchi 
wrote:

> i checked in framework, and i see that in correspondence of chronos host
> tab there is a non resolvable hostname... Why?
>
> 2016-04-09 18:14 GMT+02:00 Stefano Bianchi :
>
>> Thanks haosdent.
>> However i tried to see launch that command and what i see is:
>> 1) Resources are increased, this is what i expected, good;
>> 2) A Chronos Job that run each 2 minutes, is allocated and then "Staged";
>> is i click on sandbox i obtain this message:
>>
>> Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
>> exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
>>
>> What does it means? How can i solve it?
>> However i tried to launch your command but i still unable to use the
>> terminal after that :P, this is another and minor issue.
>>
>>
>> 2016-04-09 17:34 GMT+02:00 haosdent :
>>
>>> Hi, @Stefano You could specify the flag --log_dir when you start Mesos
>>> Agent. For example:
>>>
>>> mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
>>> --resources='cpu(*):1;mem(*):1000;disk(*):8000' --log_dir=/var/log/mesos
>>>
>>> So it would log to files under /var/log/mesos instead of console.
>>>
>>> On Sat, Apr 9, 2016 at 10:08 PM, Stefano Bianchi 
>>> wrote:
>>>
 Hi
 All is working fine!
 I can see more disk space and more RAM!
 The only thing that is different is that with the Arjun last command, i
 obtain a verbose output, i mean a lot of messages continuously shown, on
 command line. i would like to hide them and continue to use the command
 line, is it possible?

 Thanks again!

>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Haosdent Huang
>>>
>>
>>
>


-- 
Best Regards,
Haosdent Huang

Re: how to change mesos resources

[Stefano Bianchi]

i checked in framework, and i see that in correspondence of chronos host
tab there is a non resolvable hostname... Why?

2016-04-09 18:14 GMT+02:00 Stefano Bianchi :

> Thanks haosdent.
> However i tried to see launch that command and what i see is:
> 1) Resources are increased, this is what i expected, good;
> 2) A Chronos Job that run each 2 minutes, is allocated and then "Staged";
> is i click on sandbox i obtain this message:
>
> Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
> exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.
>
> What does it means? How can i solve it?
> However i tried to launch your command but i still unable to use the
> terminal after that :P, this is another and minor issue.
>
>
> 2016-04-09 17:34 GMT+02:00 haosdent :
>
>> Hi, @Stefano You could specify the flag --log_dir when you start Mesos
>> Agent. For example:
>>
>> mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
>> --resources='cpu(*):1;mem(*):1000;disk(*):8000' --log_dir=/var/log/mesos
>>
>> So it would log to files under /var/log/mesos instead of console.
>>
>> On Sat, Apr 9, 2016 at 10:08 PM, Stefano Bianchi 
>> wrote:
>>
>>> Hi
>>> All is working fine!
>>> I can see more disk space and more RAM!
>>> The only thing that is different is that with the Arjun last command, i
>>> obtain a verbose output, i mean a lot of messages continuously shown, on
>>> command line. i would like to hide them and continue to use the command
>>> line, is it possible?
>>>
>>> Thanks again!
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>

Re: how to change mesos resources

[Stefano Bianchi]

Thanks haosdent.
However i tried to see launch that command and what i see is:
1) Resources are increased, this is what i expected, good;
2) A Chronos Job that run each 2 minutes, is allocated and then "Staged";
is i click on sandbox i obtain this message:

Framework with ID 'c01b5040-6079-4f55-8ef2-089f0d4d1987-' does not
exist on slave with ID 'ad490064-1a6e-415c-8536-daef0d8e3572-S20'.

What does it means? How can i solve it?
However i tried to launch your command but i still unable to use the
terminal after that :P, this is another and minor issue.


2016-04-09 17:34 GMT+02:00 haosdent :

> Hi, @Stefano You could specify the flag --log_dir when you start Mesos
> Agent. For example:
>
> mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
> --resources='cpu(*):1;mem(*):1000;disk(*):8000' --log_dir=/var/log/mesos
>
> So it would log to files under /var/log/mesos instead of console.
>
> On Sat, Apr 9, 2016 at 10:08 PM, Stefano Bianchi 
> wrote:
>
>> Hi
>> All is working fine!
>> I can see more disk space and more RAM!
>> The only thing that is different is that with the Arjun last command, i
>> obtain a verbose output, i mean a lot of messages continuously shown, on
>> command line. i would like to hide them and continue to use the command
>> line, is it possible?
>>
>> Thanks again!
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: how to change mesos resources

[haosdent]

Hi, @Stefano You could specify the flag --log_dir when you start Mesos
Agent. For example:

mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
--resources='cpu(*):1;mem(*):1000;disk(*):8000' --log_dir=/var/log/mesos

So it would log to files under /var/log/mesos instead of console.

On Sat, Apr 9, 2016 at 10:08 PM, Stefano Bianchi 
wrote:

> Hi
> All is working fine!
> I can see more disk space and more RAM!
> The only thing that is different is that with the Arjun last command, i
> obtain a verbose output, i mean a lot of messages continuously shown, on
> command line. i would like to hide them and continue to use the command
> line, is it possible?
>
> Thanks again!
>



-- 
Best Regards,
Haosdent Huang

Re: how to change mesos resources

[Stefano Bianchi]

Hi
All is working fine!
I can see more disk space and more RAM!
The only thing that is different is that with the Arjun last command, i
obtain a verbose output, i mean a lot of messages continuously shown, on
command line. i would like to hide them and continue to use the command
line, is it possible?

Thanks again!

Re: how to change mesos resources

[Stefano Bianchi]

Can you please confirm the procedure i have written?

Thanks to all!

2016-04-09 0:28 GMT+02:00 Stefano Bianchi :

> yes i imagined that, indeed i will not allocate that amount of RAM, but at
> least a number higher than 920 M.
> OK so summarizing:
> 1) i stop mesos slave with: service mesos-slave stop
> 2)then as June suggest i run: sudo sh -c "echo
> MESOS_WORK_DIR=/scratch.local/mesos >> /etc/default/mesos-slave"
> 3) then as Arjun suggets:
>
> rm -f /tmp/mesos/meta/slaves/latest
>
> mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
> --resources='cpu(*):1;mem(*):1000;disk(*):8000'
>
>
>
>
>
>
>
> Is this correct procedure?
>
>
>
>
> 2016-04-08 23:57 GMT+02:00 Stefano Bianchi :
>
>> i tried the command: free -m
>> and i obtained this output:
>>   totalusedfree  shared
>> buff/cache   available
>>
>> Mem:   1840 1201407  40 312
>>   1507
>>
>> Swap: 0   0   0
>>
>> so there is not 2048 MB of RAM? i'm sure that openstack tells me that
>> this is a machine with 2048 MB of RAM...
>>
>> 2016-04-08 23:44 GMT+02:00 Arkal Arjun Rao :
>>
>>> You set it up with 2048MB but you  probably don't really get all of it
>>> (try `free -m` on the slave). Same with Disk (look at the value of df).
>>> from the book "Building Applications in Mesos":
>>> "The slave will reserve 1 GB or 50% of detected memory, whichever is
>>> smaller, in order to run itself and other operating system services.
>>> Likewise, it will reserve 5 GB or 50% of detected disk, whichever is
>>> smaller."
>>>
>>> If you want to explicitly reserve a value, first ensure you have the
>>> resources you want per slave then run this
>>> 
>>> rm -f /tmp/mesos/meta/slaves/latest
>>> mesos-slave --master=MASTER_ADDRESS:5050
>>> --hostname=slave_public_IP_i_set
>>> --resources='cpu(*):1;mem(*):2000;disk(*):9000'
>>>
>>> Arjun
>>>
>>> On Fri, Apr 8, 2016 at 2:23 PM, Stefano Bianchi 
>>> wrote:
>>>
 What has to be clear is that i'm running virtual machines on openstack,
 so i am not on bare metal.
 All the VMs are Openstack Images, and each slave has been built with
 2048 MB of RAM, so since slaves are 3 i should see in mesos something close
 to 6144 MB, but mesos shows only 2.7 GB.
 If you look at the command output i posted in previous messages, the
 current mesos resources configuration allows 920 MB and 5112 MB of disk
 space for each slave. I would like that mesos can see for instance 2000 MB
 of RAM and 9000 MB of disk. and for this reason i have run: mesos-slave
 --master=MASTER_ADDRESS:5050 --resources='cpu:1;mem:2000;disk:9000'

 June Taylor, i need to understand:
 1) What the command you suggest do?
 2) Should i stop mesos-slave before? and then run your command?

 Thanks in advance.

 2016-04-08 21:28 GMT+02:00 June Taylor :

> How much actual RAM do your slaves contain? You can only make
> available up to that amount, minus the bit that the slave reserves.
>
>
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
> On Fri, Apr 8, 2016 at 1:29 PM, Stefano Bianchi 
> wrote:
>
>> Hi i would like to enter in this mailing list.
>> i'm currently doing my Master Thesis on Mesos and Calico.
>> I'm working at INFN, institute of nuclear physics. The goal of the
>> thesis is to build a PaaS where mesos is the scheduler and Calico must
>> allow the interconnection between multiple datacenters linked to the 
>> CERN.
>>
>> I'm exploiting an IaaS based on Openstack, here i have created 6
>> Virtual Machines, 3 Masters and 3 Slaves, on one slave is running 
>> Mesos-DNS
>> from Marathon.
>> All is perfectly working, since i am on another network i changed
>> correctly the hostnames such that on mesos are resolvable and i tried to
>> run from marathon a simple http server which is scalable on all my 
>> machine.
>> So all is fine and working.
>>
>> The only thing that i don't like is that each 3 slaves have 1 CPU 10
>> GB of disk memory and 2GB of RAM, but mesos currently show for each one
>> only 5 GB of disk memory and 900MB of RAM.
>> So checking in documentation i found the command to manage the
>> resources.
>> I stopped Slave1, for instance, and i have run this command:
>>
>> mesos-slave --master=MASTER_ADDRESS:5050
>> --resources='cpu:1;mem:2000;disk:9000'
>>
>> where i want set 2000 GB of RAM and 9000GB of disk memory.
>>  The output is the following:
>>
>> I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by 
>> root
>>
>> I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2
>>

Re: how to change mesos resources

[Stefano Bianchi]

i tried the command: free -m
and i obtained this output:
  totalusedfree  shared  buff/cache
  available

Mem:   1840 1201407  40 312
1507

Swap: 0   0   0

so there is not 2048 MB of RAM? i'm sure that openstack tells me that this
is a machine with 2048 MB of RAM...

2016-04-08 23:44 GMT+02:00 Arkal Arjun Rao :

> You set it up with 2048MB but you  probably don't really get all of it
> (try `free -m` on the slave). Same with Disk (look at the value of df).
> from the book "Building Applications in Mesos":
> "The slave will reserve 1 GB or 50% of detected memory, whichever is
> smaller, in order to run itself and other operating system services.
> Likewise, it will reserve 5 GB or 50% of detected disk, whichever is
> smaller."
>
> If you want to explicitly reserve a value, first ensure you have the
> resources you want per slave then run this
> 
> rm -f /tmp/mesos/meta/slaves/latest
> mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
> --resources='cpu(*):1;mem(*):2000;disk(*):9000'
>
> Arjun
>
> On Fri, Apr 8, 2016 at 2:23 PM, Stefano Bianchi 
> wrote:
>
>> What has to be clear is that i'm running virtual machines on openstack,
>> so i am not on bare metal.
>> All the VMs are Openstack Images, and each slave has been built with 2048
>> MB of RAM, so since slaves are 3 i should see in mesos something close to
>> 6144 MB, but mesos shows only 2.7 GB.
>> If you look at the command output i posted in previous messages, the
>> current mesos resources configuration allows 920 MB and 5112 MB of disk
>> space for each slave. I would like that mesos can see for instance 2000 MB
>> of RAM and 9000 MB of disk. and for this reason i have run: mesos-slave
>> --master=MASTER_ADDRESS:5050 --resources='cpu:1;mem:2000;disk:9000'
>>
>> June Taylor, i need to understand:
>> 1) What the command you suggest do?
>> 2) Should i stop mesos-slave before? and then run your command?
>>
>> Thanks in advance.
>>
>> 2016-04-08 21:28 GMT+02:00 June Taylor :
>>
>>> How much actual RAM do your slaves contain? You can only make available
>>> up to that amount, minus the bit that the slave reserves.
>>>
>>>
>>> Thanks,
>>> June Taylor
>>> System Administrator, Minnesota Population Center
>>> University of Minnesota
>>>
>>> On Fri, Apr 8, 2016 at 1:29 PM, Stefano Bianchi 
>>> wrote:
>>>
 Hi i would like to enter in this mailing list.
 i'm currently doing my Master Thesis on Mesos and Calico.
 I'm working at INFN, institute of nuclear physics. The goal of the
 thesis is to build a PaaS where mesos is the scheduler and Calico must
 allow the interconnection between multiple datacenters linked to the CERN.

 I'm exploiting an IaaS based on Openstack, here i have created 6
 Virtual Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS
 from Marathon.
 All is perfectly working, since i am on another network i changed
 correctly the hostnames such that on mesos are resolvable and i tried to
 run from marathon a simple http server which is scalable on all my machine.
 So all is fine and working.

 The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB
 of disk memory and 2GB of RAM, but mesos currently show for each one only 5
 GB of disk memory and 900MB of RAM.
 So checking in documentation i found the command to manage the
 resources.
 I stopped Slave1, for instance, and i have run this command:

 mesos-slave --master=MASTER_ADDRESS:5050
 --resources='cpu:1;mem:2000;disk:9000'

 where i want set 2000 GB of RAM and 9000GB of disk memory.
  The output is the following:

 I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by 
 root

 I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2

 I0408 15:11:00.915448  7892 main.cpp:220] Git tag: 0.27.2

 I0408 15:11:00.915459  7892 main.cpp:224] Git SHA: 
 3c9ec4a0f34420b7803848af597de00fedefe0e2

 I0408 15:11:00.923334  7892 systemd.cpp:236] systemd version `219` detected

 I0408 15:11:00.923384  7892 main.cpp:232] Inializing systemd state

 I0408 15:11:00.950050  7892 systemd.cpp:324] Started systemd slice 
 `mesos_executors.slice`

 I0408 15:11:00.951529  7892 containerizer.cpp:143] Using isolation: 
 posix/cpu,posix/mem,filesystem/posix

 I0408 15:11:00.963232  7892 linux_launcher.cpp:101] Using 
 /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher

 I0408 15:11:00.965541  7892 main.cpp:320] Starting Mesos slave

 I0408 15:11:00.966008  7892 slave.cpp:192] Slave started on 
 1)@192.168.100.56:5051

 I0408 15:11:00.966023  7892 slave.cpp:193] Flags at startup: 
 --appc_store_dir="/tmp/mesos/store/appc" 

Re: how to change mesos resources

[Greg Mann]

Hi Stefano,
The agent saves its resource information on the disk, so that it can
recover in case of failure. When the agent starts up, it checks the work
directory, and if it finds information left behind by a previous instance
of the agent, it loads that information and attempts to register with the
master as the same agent. In order to change the agent resources you must
delete the 'work_dir', so that the agent believes it's the first agent to
run on the machine.

As June and Arjun pointed out, the agent will reserve some resources for
itself to make sure that the agent and other operating system processes
don't starve. The actual memory and disk needed for the agent and OS varies
from machine to machine, so it may be OK for you to offer more of the
agent's resources to Mesos. You can do this by specifying the resources you
would like to offer with the `--resources` flag. However, if the agent has
2GB of memory total, I would _not_ recommend that you tell the agent to
offer the entire 2GB to Mesos. It does, in fact, need some amount of
mem/disk for other processes. If you'd like to figure out how much it
needs, you can launch the VM and observe its resource usage under a typical
workload.

The steps outlined by Arjun should work, but note that offering that much
RAM may cause performance issues on your agent if you run tasks on it which
attempt to use all 2GB.

Cheers,
Greg

On Fri, Apr 8, 2016 at 2:44 PM, Arkal Arjun Rao  wrote:

> You set it up with 2048MB but you  probably don't really get all of it
> (try `free -m` on the slave). Same with Disk (look at the value of df).
> from the book "Building Applications in Mesos":
> "The slave will reserve 1 GB or 50% of detected memory, whichever is
> smaller, in order to run itself and other operating system services.
> Likewise, it will reserve 5 GB or 50% of detected disk, whichever is
> smaller."
>
> If you want to explicitly reserve a value, first ensure you have the
> resources you want per slave then run this
> 
> rm -f /tmp/mesos/meta/slaves/latest
> mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
> --resources='cpu(*):1;mem(*):2000;disk(*):9000'
>
> Arjun
>
> On Fri, Apr 8, 2016 at 2:23 PM, Stefano Bianchi 
> wrote:
>
>> What has to be clear is that i'm running virtual machines on openstack,
>> so i am not on bare metal.
>> All the VMs are Openstack Images, and each slave has been built with 2048
>> MB of RAM, so since slaves are 3 i should see in mesos something close to
>> 6144 MB, but mesos shows only 2.7 GB.
>> If you look at the command output i posted in previous messages, the
>> current mesos resources configuration allows 920 MB and 5112 MB of disk
>> space for each slave. I would like that mesos can see for instance 2000 MB
>> of RAM and 9000 MB of disk. and for this reason i have run: mesos-slave
>> --master=MASTER_ADDRESS:5050 --resources='cpu:1;mem:2000;disk:9000'
>>
>> June Taylor, i need to understand:
>> 1) What the command you suggest do?
>> 2) Should i stop mesos-slave before? and then run your command?
>>
>> Thanks in advance.
>>
>> 2016-04-08 21:28 GMT+02:00 June Taylor :
>>
>>> How much actual RAM do your slaves contain? You can only make available
>>> up to that amount, minus the bit that the slave reserves.
>>>
>>>
>>> Thanks,
>>> June Taylor
>>> System Administrator, Minnesota Population Center
>>> University of Minnesota
>>>
>>> On Fri, Apr 8, 2016 at 1:29 PM, Stefano Bianchi 
>>> wrote:
>>>
 Hi i would like to enter in this mailing list.
 i'm currently doing my Master Thesis on Mesos and Calico.
 I'm working at INFN, institute of nuclear physics. The goal of the
 thesis is to build a PaaS where mesos is the scheduler and Calico must
 allow the interconnection between multiple datacenters linked to the CERN.

 I'm exploiting an IaaS based on Openstack, here i have created 6
 Virtual Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS
 from Marathon.
 All is perfectly working, since i am on another network i changed
 correctly the hostnames such that on mesos are resolvable and i tried to
 run from marathon a simple http server which is scalable on all my machine.
 So all is fine and working.

 The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB
 of disk memory and 2GB of RAM, but mesos currently show for each one only 5
 GB of disk memory and 900MB of RAM.
 So checking in documentation i found the command to manage the
 resources.
 I stopped Slave1, for instance, and i have run this command:

 mesos-slave --master=MASTER_ADDRESS:5050
 --resources='cpu:1;mem:2000;disk:9000'

 where i want set 2000 GB of RAM and 9000GB of disk memory.
  The output is the following:

 I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by 
 root

 I0408 15:11:00.915436  7892 

Re: how to change mesos resources

[Arkal Arjun Rao]

You set it up with 2048MB but you  probably don't really get all of it (try
`free -m` on the slave). Same with Disk (look at the value of df).
from the book "Building Applications in Mesos":
"The slave will reserve 1 GB or 50% of detected memory, whichever is
smaller, in order to run itself and other operating system services.
Likewise, it will reserve 5 GB or 50% of detected disk, whichever is
smaller."

If you want to explicitly reserve a value, first ensure you have the
resources you want per slave then run this

rm -f /tmp/mesos/meta/slaves/latest
mesos-slave --master=MASTER_ADDRESS:5050 --hostname=slave_public_IP_i_set
--resources='cpu(*):1;mem(*):2000;disk(*):9000'

Arjun

On Fri, Apr 8, 2016 at 2:23 PM, Stefano Bianchi 
wrote:

> What has to be clear is that i'm running virtual machines on openstack, so
> i am not on bare metal.
> All the VMs are Openstack Images, and each slave has been built with 2048
> MB of RAM, so since slaves are 3 i should see in mesos something close to
> 6144 MB, but mesos shows only 2.7 GB.
> If you look at the command output i posted in previous messages, the
> current mesos resources configuration allows 920 MB and 5112 MB of disk
> space for each slave. I would like that mesos can see for instance 2000 MB
> of RAM and 9000 MB of disk. and for this reason i have run: mesos-slave
> --master=MASTER_ADDRESS:5050 --resources='cpu:1;mem:2000;disk:9000'
>
> June Taylor, i need to understand:
> 1) What the command you suggest do?
> 2) Should i stop mesos-slave before? and then run your command?
>
> Thanks in advance.
>
> 2016-04-08 21:28 GMT+02:00 June Taylor :
>
>> How much actual RAM do your slaves contain? You can only make available
>> up to that amount, minus the bit that the slave reserves.
>>
>>
>> Thanks,
>> June Taylor
>> System Administrator, Minnesota Population Center
>> University of Minnesota
>>
>> On Fri, Apr 8, 2016 at 1:29 PM, Stefano Bianchi 
>> wrote:
>>
>>> Hi i would like to enter in this mailing list.
>>> i'm currently doing my Master Thesis on Mesos and Calico.
>>> I'm working at INFN, institute of nuclear physics. The goal of the
>>> thesis is to build a PaaS where mesos is the scheduler and Calico must
>>> allow the interconnection between multiple datacenters linked to the CERN.
>>>
>>> I'm exploiting an IaaS based on Openstack, here i have created 6 Virtual
>>> Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS from
>>> Marathon.
>>> All is perfectly working, since i am on another network i changed
>>> correctly the hostnames such that on mesos are resolvable and i tried to
>>> run from marathon a simple http server which is scalable on all my machine.
>>> So all is fine and working.
>>>
>>> The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB
>>> of disk memory and 2GB of RAM, but mesos currently show for each one only 5
>>> GB of disk memory and 900MB of RAM.
>>> So checking in documentation i found the command to manage the resources.
>>> I stopped Slave1, for instance, and i have run this command:
>>>
>>> mesos-slave --master=MASTER_ADDRESS:5050
>>> --resources='cpu:1;mem:2000;disk:9000'
>>>
>>> where i want set 2000 GB of RAM and 9000GB of disk memory.
>>>  The output is the following:
>>>
>>> I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by root
>>>
>>> I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2
>>>
>>> I0408 15:11:00.915448  7892 main.cpp:220] Git tag: 0.27.2
>>>
>>> I0408 15:11:00.915459  7892 main.cpp:224] Git SHA: 
>>> 3c9ec4a0f34420b7803848af597de00fedefe0e2
>>>
>>> I0408 15:11:00.923334  7892 systemd.cpp:236] systemd version `219` detected
>>>
>>> I0408 15:11:00.923384  7892 main.cpp:232] Inializing systemd state
>>>
>>> I0408 15:11:00.950050  7892 systemd.cpp:324] Started systemd slice 
>>> `mesos_executors.slice`
>>>
>>> I0408 15:11:00.951529  7892 containerizer.cpp:143] Using isolation: 
>>> posix/cpu,posix/mem,filesystem/posix
>>>
>>> I0408 15:11:00.963232  7892 linux_launcher.cpp:101] Using 
>>> /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
>>>
>>> I0408 15:11:00.965541  7892 main.cpp:320] Starting Mesos slave
>>>
>>> I0408 15:11:00.966008  7892 slave.cpp:192] Slave started on 
>>> 1)@192.168.100.56:5051
>>>
>>> I0408 15:11:00.966023  7892 slave.cpp:193] Flags at startup: 
>>> --appc_store_dir="/tmp/mesos/store/appc" --authenticatee="crammd5" 
>>> --cgroups_cpu_enable_pids_and_tids_count="false" 
>>> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup" 
>>> --cgroups_limit_swap="false" --cgroups_root="mesos" 
>>> --container_disk_watch_interval="15secs" --containerizers="mesos" 
>>> --default_role="*" --disk_watch_interval="1mins" --docker="docker" 
>>> --docker_auth_server="https://auth.docker.io; --docker_kill_orphans="true" 
>>> --docker_puller_timeout="60" 
>>> --docker_registry="https://registry-1.docker.io; 
>>> --docker_remove_delay="6hrs" 

Re: how to change mesos resources

[Stefano Bianchi]

What has to be clear is that i'm running virtual machines on openstack, so
i am not on bare metal.
All the VMs are Openstack Images, and each slave has been built with 2048
MB of RAM, so since slaves are 3 i should see in mesos something close to
6144 MB, but mesos shows only 2.7 GB.
If you look at the command output i posted in previous messages, the
current mesos resources configuration allows 920 MB and 5112 MB of disk
space for each slave. I would like that mesos can see for instance 2000 MB
of RAM and 9000 MB of disk. and for this reason i have run: mesos-slave
--master=MASTER_ADDRESS:5050 --resources='cpu:1;mem:2000;disk:9000'

June Taylor, i need to understand:
1) What the command you suggest do?
2) Should i stop mesos-slave before? and then run your command?

Thanks in advance.

2016-04-08 21:28 GMT+02:00 June Taylor :

> How much actual RAM do your slaves contain? You can only make available up
> to that amount, minus the bit that the slave reserves.
>
>
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
> On Fri, Apr 8, 2016 at 1:29 PM, Stefano Bianchi 
> wrote:
>
>> Hi i would like to enter in this mailing list.
>> i'm currently doing my Master Thesis on Mesos and Calico.
>> I'm working at INFN, institute of nuclear physics. The goal of the thesis
>> is to build a PaaS where mesos is the scheduler and Calico must allow the
>> interconnection between multiple datacenters linked to the CERN.
>>
>> I'm exploiting an IaaS based on Openstack, here i have created 6 Virtual
>> Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS from
>> Marathon.
>> All is perfectly working, since i am on another network i changed
>> correctly the hostnames such that on mesos are resolvable and i tried to
>> run from marathon a simple http server which is scalable on all my machine.
>> So all is fine and working.
>>
>> The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB
>> of disk memory and 2GB of RAM, but mesos currently show for each one only 5
>> GB of disk memory and 900MB of RAM.
>> So checking in documentation i found the command to manage the resources.
>> I stopped Slave1, for instance, and i have run this command:
>>
>> mesos-slave --master=MASTER_ADDRESS:5050
>> --resources='cpu:1;mem:2000;disk:9000'
>>
>> where i want set 2000 GB of RAM and 9000GB of disk memory.
>>  The output is the following:
>>
>> I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by root
>>
>> I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2
>>
>> I0408 15:11:00.915448  7892 main.cpp:220] Git tag: 0.27.2
>>
>> I0408 15:11:00.915459  7892 main.cpp:224] Git SHA: 
>> 3c9ec4a0f34420b7803848af597de00fedefe0e2
>>
>> I0408 15:11:00.923334  7892 systemd.cpp:236] systemd version `219` detected
>>
>> I0408 15:11:00.923384  7892 main.cpp:232] Inializing systemd state
>>
>> I0408 15:11:00.950050  7892 systemd.cpp:324] Started systemd slice 
>> `mesos_executors.slice`
>>
>> I0408 15:11:00.951529  7892 containerizer.cpp:143] Using isolation: 
>> posix/cpu,posix/mem,filesystem/posix
>>
>> I0408 15:11:00.963232  7892 linux_launcher.cpp:101] Using 
>> /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
>>
>> I0408 15:11:00.965541  7892 main.cpp:320] Starting Mesos slave
>>
>> I0408 15:11:00.966008  7892 slave.cpp:192] Slave started on 
>> 1)@192.168.100.56:5051
>>
>> I0408 15:11:00.966023  7892 slave.cpp:193] Flags at startup: 
>> --appc_store_dir="/tmp/mesos/store/appc" --authenticatee="crammd5" 
>> --cgroups_cpu_enable_pids_and_tids_count="false" 
>> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup" 
>> --cgroups_limit_swap="false" --cgroups_root="mesos" 
>> --container_disk_watch_interval="15secs" --containerizers="mesos" 
>> --default_role="*" --disk_watch_interval="1mins" --docker="docker" 
>> --docker_auth_server="https://auth.docker.io; --docker_kill_orphans="true" 
>> --docker_puller_timeout="60" 
>> --docker_registry="https://registry-1.docker.io; 
>> --docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock" 
>> --docker_stop_timeout="0ns" --docker_store_dir="/tmp/mesos/store/docker" 
>> --enforce_container_disk_quota="false" 
>> --executor_registration_timeout="1mins" 
>> --executor_shutdown_grace_period="5secs" 
>> --fetcher_cache_dir="/tmp/mesos/fetch" --fetcher_cache_size="2GB" 
>> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1" 
>> --hadoop_home="" --help="false" --hostname_lookup="true" 
>> --image_provisioner_backend="copy" --initialize_driver_logging="true" 
>> --isolation="posix/cpu,posix/mem" --launcher_dir="/usr/libexec/mesos" 
>> --logbufsecs="0" --logging_level="INFO" --master="192.168.100.55:5050" 
>> --oversubscribed_resources_interval="15secs" --perf_duration="10secs" 
>> --perf_interval="1mins" --port="5051" --qos_correction_interval_min="0ns" 
>> --quiet="false" --recover="reconnect" --recovery_timeout="15mins" 
>> 

Re: how to change mesos resources

[June Taylor]

How much actual RAM do your slaves contain? You can only make available up
to that amount, minus the bit that the slave reserves.


Thanks,
June Taylor
System Administrator, Minnesota Population Center
University of Minnesota

On Fri, Apr 8, 2016 at 1:29 PM, Stefano Bianchi 
wrote:

> Hi i would like to enter in this mailing list.
> i'm currently doing my Master Thesis on Mesos and Calico.
> I'm working at INFN, institute of nuclear physics. The goal of the thesis
> is to build a PaaS where mesos is the scheduler and Calico must allow the
> interconnection between multiple datacenters linked to the CERN.
>
> I'm exploiting an IaaS based on Openstack, here i have created 6 Virtual
> Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS from
> Marathon.
> All is perfectly working, since i am on another network i changed
> correctly the hostnames such that on mesos are resolvable and i tried to
> run from marathon a simple http server which is scalable on all my machine.
> So all is fine and working.
>
> The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB of
> disk memory and 2GB of RAM, but mesos currently show for each one only 5 GB
> of disk memory and 900MB of RAM.
> So checking in documentation i found the command to manage the resources.
> I stopped Slave1, for instance, and i have run this command:
>
> mesos-slave --master=MASTER_ADDRESS:5050
> --resources='cpu:1;mem:2000;disk:9000'
>
> where i want set 2000 GB of RAM and 9000GB of disk memory.
>  The output is the following:
>
> I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by root
>
> I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2
>
> I0408 15:11:00.915448  7892 main.cpp:220] Git tag: 0.27.2
>
> I0408 15:11:00.915459  7892 main.cpp:224] Git SHA: 
> 3c9ec4a0f34420b7803848af597de00fedefe0e2
>
> I0408 15:11:00.923334  7892 systemd.cpp:236] systemd version `219` detected
>
> I0408 15:11:00.923384  7892 main.cpp:232] Inializing systemd state
>
> I0408 15:11:00.950050  7892 systemd.cpp:324] Started systemd slice 
> `mesos_executors.slice`
>
> I0408 15:11:00.951529  7892 containerizer.cpp:143] Using isolation: 
> posix/cpu,posix/mem,filesystem/posix
>
> I0408 15:11:00.963232  7892 linux_launcher.cpp:101] Using 
> /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
>
> I0408 15:11:00.965541  7892 main.cpp:320] Starting Mesos slave
>
> I0408 15:11:00.966008  7892 slave.cpp:192] Slave started on 
> 1)@192.168.100.56:5051
>
> I0408 15:11:00.966023  7892 slave.cpp:193] Flags at startup: 
> --appc_store_dir="/tmp/mesos/store/appc" --authenticatee="crammd5" 
> --cgroups_cpu_enable_pids_and_tids_count="false" --cgroups_enable_cfs="false" 
> --cgroups_hierarchy="/sys/fs/cgroup" --cgroups_limit_swap="false" 
> --cgroups_root="mesos" --container_disk_watch_interval="15secs" 
> --containerizers="mesos" --default_role="*" --disk_watch_interval="1mins" 
> --docker="docker" --docker_auth_server="https://auth.docker.io; 
> --docker_kill_orphans="true" --docker_puller_timeout="60" 
> --docker_registry="https://registry-1.docker.io; --docker_remove_delay="6hrs" 
> --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns" 
> --docker_store_dir="/tmp/mesos/store/docker" 
> --enforce_container_disk_quota="false" 
> --executor_registration_timeout="1mins" 
> --executor_shutdown_grace_period="5secs" 
> --fetcher_cache_dir="/tmp/mesos/fetch" --fetcher_cache_size="2GB" 
> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1" 
> --hadoop_home="" --help="false" --hostname_lookup="true" 
> --image_provisioner_backend="copy" --initialize_driver_logging="true" 
> --isolation="posix/cpu,posix/mem" --launcher_dir="/usr/libexec/mesos" 
> --logbufsecs="0" --logging_level="INFO" --master="192.168.100.55:5050" 
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs" 
> --perf_interval="1mins" --port="5051" --qos_correction_interval_min="0ns" 
> --quiet="false" --recover="reconnect" --recovery_timeout="15mins" 
> --registration_backoff_factor="1secs" --resources="cpu:1;mem:2000;disk:9000" 
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox" 
> --strict="true" --switch_user="true" --systemd_enable_support="true" 
> --systemd_runtime_directory="/run/systemd/system" --version="false" 
> --work_dir="/tmp/mesos"
>
> I0408 15:11:00.967485  7892 slave.cpp:463] Slave resources: cpu(*):1; 
> mem(*):2000; disk(*):9000; cpus(*):1; ports(*):[31000-32000]
>
> I0408 15:11:00.967547  7892 slave.cpp:471] Slave attributes: [  ]
>
> I0408 15:11:00.967560  7892 slave.cpp:476] Slave hostname: 
> slave1.openstacklocal
>
> I0408 15:11:00.971304  7893 state.cpp:58] Recovering state from 
> '/tmp/mesos/meta'
>
> *Failed to perform recovery: Incompatible slave info detected*.
>
> 
>
> Old slave info:
>
> hostname: "*slave_public_IP_i_set*"
>
> resources {
>
>   name: "cpus"
>
>   type: 

Re: how to change mesos resources

[June Taylor]

The slave process does reserve some amount of RAM for itself. Is the mesos
work-dir set to a path on the disk where your free space is? You can set it
with the MESOS_WORK_DIR configuration flag:

sudo sh -c "echo MESOS_WORK_DIR=/scratch.local/mesos >>
/etc/default/mesos-slave"


Thanks,
June Taylor
System Administrator, Minnesota Population Center
University of Minnesota

On Fri, Apr 8, 2016 at 1:29 PM, Stefano Bianchi 
wrote:

> Hi i would like to enter in this mailing list.
> i'm currently doing my Master Thesis on Mesos and Calico.
> I'm working at INFN, institute of nuclear physics. The goal of the thesis
> is to build a PaaS where mesos is the scheduler and Calico must allow the
> interconnection between multiple datacenters linked to the CERN.
>
> I'm exploiting an IaaS based on Openstack, here i have created 6 Virtual
> Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS from
> Marathon.
> All is perfectly working, since i am on another network i changed
> correctly the hostnames such that on mesos are resolvable and i tried to
> run from marathon a simple http server which is scalable on all my machine.
> So all is fine and working.
>
> The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB of
> disk memory and 2GB of RAM, but mesos currently show for each one only 5 GB
> of disk memory and 900MB of RAM.
> So checking in documentation i found the command to manage the resources.
> I stopped Slave1, for instance, and i have run this command:
>
> mesos-slave --master=MASTER_ADDRESS:5050
> --resources='cpu:1;mem:2000;disk:9000'
>
> where i want set 2000 GB of RAM and 9000GB of disk memory.
>  The output is the following:
>
> I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by root
>
> I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2
>
> I0408 15:11:00.915448  7892 main.cpp:220] Git tag: 0.27.2
>
> I0408 15:11:00.915459  7892 main.cpp:224] Git SHA: 
> 3c9ec4a0f34420b7803848af597de00fedefe0e2
>
> I0408 15:11:00.923334  7892 systemd.cpp:236] systemd version `219` detected
>
> I0408 15:11:00.923384  7892 main.cpp:232] Inializing systemd state
>
> I0408 15:11:00.950050  7892 systemd.cpp:324] Started systemd slice 
> `mesos_executors.slice`
>
> I0408 15:11:00.951529  7892 containerizer.cpp:143] Using isolation: 
> posix/cpu,posix/mem,filesystem/posix
>
> I0408 15:11:00.963232  7892 linux_launcher.cpp:101] Using 
> /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
>
> I0408 15:11:00.965541  7892 main.cpp:320] Starting Mesos slave
>
> I0408 15:11:00.966008  7892 slave.cpp:192] Slave started on 
> 1)@192.168.100.56:5051
>
> I0408 15:11:00.966023  7892 slave.cpp:193] Flags at startup: 
> --appc_store_dir="/tmp/mesos/store/appc" --authenticatee="crammd5" 
> --cgroups_cpu_enable_pids_and_tids_count="false" --cgroups_enable_cfs="false" 
> --cgroups_hierarchy="/sys/fs/cgroup" --cgroups_limit_swap="false" 
> --cgroups_root="mesos" --container_disk_watch_interval="15secs" 
> --containerizers="mesos" --default_role="*" --disk_watch_interval="1mins" 
> --docker="docker" --docker_auth_server="https://auth.docker.io; 
> --docker_kill_orphans="true" --docker_puller_timeout="60" 
> --docker_registry="https://registry-1.docker.io; --docker_remove_delay="6hrs" 
> --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns" 
> --docker_store_dir="/tmp/mesos/store/docker" 
> --enforce_container_disk_quota="false" 
> --executor_registration_timeout="1mins" 
> --executor_shutdown_grace_period="5secs" 
> --fetcher_cache_dir="/tmp/mesos/fetch" --fetcher_cache_size="2GB" 
> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1" 
> --hadoop_home="" --help="false" --hostname_lookup="true" 
> --image_provisioner_backend="copy" --initialize_driver_logging="true" 
> --isolation="posix/cpu,posix/mem" --launcher_dir="/usr/libexec/mesos" 
> --logbufsecs="0" --logging_level="INFO" --master="192.168.100.55:5050" 
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs" 
> --perf_interval="1mins" --port="5051" --qos_correction_interval_min="0ns" 
> --quiet="false" --recover="reconnect" --recovery_timeout="15mins" 
> --registration_backoff_factor="1secs" --resources="cpu:1;mem:2000;disk:9000" 
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox" 
> --strict="true" --switch_user="true" --systemd_enable_support="true" 
> --systemd_runtime_directory="/run/systemd/system" --version="false" 
> --work_dir="/tmp/mesos"
>
> I0408 15:11:00.967485  7892 slave.cpp:463] Slave resources: cpu(*):1; 
> mem(*):2000; disk(*):9000; cpus(*):1; ports(*):[31000-32000]
>
> I0408 15:11:00.967547  7892 slave.cpp:471] Slave attributes: [  ]
>
> I0408 15:11:00.967560  7892 slave.cpp:476] Slave hostname: 
> slave1.openstacklocal
>
> I0408 15:11:00.971304  7893 state.cpp:58] Recovering state from 
> '/tmp/mesos/meta'
>
> *Failed to perform recovery: Incompatible slave info detected*.
>
> 

Re: how to change mesos resources

[Vinod Kone]

Have you tried the remedy steps included in the error message?



To remedy this do as follows:

Step 1: rm -f /tmp/mesos/meta/slaves/latest

This ensures slave doesn't recover old live executors.

Step 2: Restart the slave.



On Fri, Apr 8, 2016 at 11:29 AM, Stefano Bianchi 
wrote:

> Hi i would like to enter in this mailing list.
> i'm currently doing my Master Thesis on Mesos and Calico.
> I'm working at INFN, institute of nuclear physics. The goal of the thesis
> is to build a PaaS where mesos is the scheduler and Calico must allow the
> interconnection between multiple datacenters linked to the CERN.
>
> I'm exploiting an IaaS based on Openstack, here i have created 6 Virtual
> Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS from
> Marathon.
> All is perfectly working, since i am on another network i changed
> correctly the hostnames such that on mesos are resolvable and i tried to
> run from marathon a simple http server which is scalable on all my machine.
> So all is fine and working.
>
> The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB of
> disk memory and 2GB of RAM, but mesos currently show for each one only 5 GB
> of disk memory and 900MB of RAM.
> So checking in documentation i found the command to manage the resources.
> I stopped Slave1, for instance, and i have run this command:
>
> mesos-slave --master=MASTER_ADDRESS:5050
> --resources='cpu:1;mem:2000;disk:9000'
>
> where i want set 2000 GB of RAM and 9000GB of disk memory.
>  The output is the following:
>
> I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by root
>
> I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2
>
> I0408 15:11:00.915448  7892 main.cpp:220] Git tag: 0.27.2
>
> I0408 15:11:00.915459  7892 main.cpp:224] Git SHA: 
> 3c9ec4a0f34420b7803848af597de00fedefe0e2
>
> I0408 15:11:00.923334  7892 systemd.cpp:236] systemd version `219` detected
>
> I0408 15:11:00.923384  7892 main.cpp:232] Inializing systemd state
>
> I0408 15:11:00.950050  7892 systemd.cpp:324] Started systemd slice 
> `mesos_executors.slice`
>
> I0408 15:11:00.951529  7892 containerizer.cpp:143] Using isolation: 
> posix/cpu,posix/mem,filesystem/posix
>
> I0408 15:11:00.963232  7892 linux_launcher.cpp:101] Using 
> /sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher
>
> I0408 15:11:00.965541  7892 main.cpp:320] Starting Mesos slave
>
> I0408 15:11:00.966008  7892 slave.cpp:192] Slave started on 
> 1)@192.168.100.56:5051
>
> I0408 15:11:00.966023  7892 slave.cpp:193] Flags at startup: 
> --appc_store_dir="/tmp/mesos/store/appc" --authenticatee="crammd5" 
> --cgroups_cpu_enable_pids_and_tids_count="false" --cgroups_enable_cfs="false" 
> --cgroups_hierarchy="/sys/fs/cgroup" --cgroups_limit_swap="false" 
> --cgroups_root="mesos" --container_disk_watch_interval="15secs" 
> --containerizers="mesos" --default_role="*" --disk_watch_interval="1mins" 
> --docker="docker" --docker_auth_server="https://auth.docker.io; 
> --docker_kill_orphans="true" --docker_puller_timeout="60" 
> --docker_registry="https://registry-1.docker.io; --docker_remove_delay="6hrs" 
> --docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns" 
> --docker_store_dir="/tmp/mesos/store/docker" 
> --enforce_container_disk_quota="false" 
> --executor_registration_timeout="1mins" 
> --executor_shutdown_grace_period="5secs" 
> --fetcher_cache_dir="/tmp/mesos/fetch" --fetcher_cache_size="2GB" 
> --frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1" 
> --hadoop_home="" --help="false" --hostname_lookup="true" 
> --image_provisioner_backend="copy" --initialize_driver_logging="true" 
> --isolation="posix/cpu,posix/mem" --launcher_dir="/usr/libexec/mesos" 
> --logbufsecs="0" --logging_level="INFO" --master="192.168.100.55:5050" 
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs" 
> --perf_interval="1mins" --port="5051" --qos_correction_interval_min="0ns" 
> --quiet="false" --recover="reconnect" --recovery_timeout="15mins" 
> --registration_backoff_factor="1secs" --resources="cpu:1;mem:2000;disk:9000" 
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox" 
> --strict="true" --switch_user="true" --systemd_enable_support="true" 
> --systemd_runtime_directory="/run/systemd/system" --version="false" 
> --work_dir="/tmp/mesos"
>
> I0408 15:11:00.967485  7892 slave.cpp:463] Slave resources: cpu(*):1; 
> mem(*):2000; disk(*):9000; cpus(*):1; ports(*):[31000-32000]
>
> I0408 15:11:00.967547  7892 slave.cpp:471] Slave attributes: [  ]
>
> I0408 15:11:00.967560  7892 slave.cpp:476] Slave hostname: 
> slave1.openstacklocal
>
> I0408 15:11:00.971304  7893 state.cpp:58] Recovering state from 
> '/tmp/mesos/meta'
>
> *Failed to perform recovery: Incompatible slave info detected*.
>
> 
>
> Old slave info:
>
> hostname: 

how to change mesos resources

[Stefano Bianchi]

Hi i would like to enter in this mailing list.
i'm currently doing my Master Thesis on Mesos and Calico.
I'm working at INFN, institute of nuclear physics. The goal of the thesis
is to build a PaaS where mesos is the scheduler and Calico must allow the
interconnection between multiple datacenters linked to the CERN.

I'm exploiting an IaaS based on Openstack, here i have created 6 Virtual
Machines, 3 Masters and 3 Slaves, on one slave is running Mesos-DNS from
Marathon.
All is perfectly working, since i am on another network i changed correctly
the hostnames such that on mesos are resolvable and i tried to run from
marathon a simple http server which is scalable on all my machine. So all
is fine and working.

The only thing that i don't like is that each 3 slaves have 1 CPU 10 GB of
disk memory and 2GB of RAM, but mesos currently show for each one only 5 GB
of disk memory and 900MB of RAM.
So checking in documentation i found the command to manage the resources.
I stopped Slave1, for instance, and i have run this command:

mesos-slave --master=MASTER_ADDRESS:5050
--resources='cpu:1;mem:2000;disk:9000'

where i want set 2000 GB of RAM and 9000GB of disk memory.
 The output is the following:

I0408 15:11:00.915324  7892 main.cpp:215] Build: 2016-03-10 20:32:58 by root

I0408 15:11:00.915436  7892 main.cpp:217] Version: 0.27.2

I0408 15:11:00.915448  7892 main.cpp:220] Git tag: 0.27.2

I0408 15:11:00.915459  7892 main.cpp:224] Git SHA:
3c9ec4a0f34420b7803848af597de00fedefe0e2

I0408 15:11:00.923334  7892 systemd.cpp:236] systemd version `219` detected

I0408 15:11:00.923384  7892 main.cpp:232] Inializing systemd state

I0408 15:11:00.950050  7892 systemd.cpp:324] Started systemd slice
`mesos_executors.slice`

I0408 15:11:00.951529  7892 containerizer.cpp:143] Using isolation:
posix/cpu,posix/mem,filesystem/posix

I0408 15:11:00.963232  7892 linux_launcher.cpp:101] Using
/sys/fs/cgroup/freezer as the freezer hierarchy for the Linux launcher

I0408 15:11:00.965541  7892 main.cpp:320] Starting Mesos slave

I0408 15:11:00.966008  7892 slave.cpp:192] Slave started on
1)@192.168.100.56:5051

I0408 15:11:00.966023  7892 slave.cpp:193] Flags at startup:
--appc_store_dir="/tmp/mesos/store/appc" --authenticatee="crammd5"
--cgroups_cpu_enable_pids_and_tids_count="false"
--cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
--cgroups_limit_swap="false" --cgroups_root="mesos"
--container_disk_watch_interval="15secs" --containerizers="mesos"
--default_role="*" --disk_watch_interval="1mins" --docker="docker"
--docker_auth_server="https://auth.docker.io;
--docker_kill_orphans="true" --docker_puller_timeout="60"
--docker_registry="https://registry-1.docker.io;
--docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock"
--docker_stop_timeout="0ns"
--docker_store_dir="/tmp/mesos/store/docker"
--enforce_container_disk_quota="false"
--executor_registration_timeout="1mins"
--executor_shutdown_grace_period="5secs"
--fetcher_cache_dir="/tmp/mesos/fetch" --fetcher_cache_size="2GB"
--frameworks_home="" --gc_delay="1weeks" --gc_disk_headroom="0.1"
--hadoop_home="" --help="false" --hostname_lookup="true"
--image_provisioner_backend="copy" --initialize_driver_logging="true"
--isolation="posix/cpu,posix/mem" --launcher_dir="/usr/libexec/mesos"
--logbufsecs="0" --logging_level="INFO" --master="192.168.100.55:5050"
--oversubscribed_resources_interval="15secs" --perf_duration="10secs"
--perf_interval="1mins" --port="5051"
--qos_correction_interval_min="0ns" --quiet="false"
--recover="reconnect" --recovery_timeout="15mins"
--registration_backoff_factor="1secs"
--resources="cpu:1;mem:2000;disk:9000"
--revocable_cpu_low_priority="true"
--sandbox_directory="/mnt/mesos/sandbox" --strict="true"
--switch_user="true" --systemd_enable_support="true"
--systemd_runtime_directory="/run/systemd/system" --version="false"
--work_dir="/tmp/mesos"

I0408 15:11:00.967485  7892 slave.cpp:463] Slave resources: cpu(*):1;
mem(*):2000; disk(*):9000; cpus(*):1; ports(*):[31000-32000]

I0408 15:11:00.967547  7892 slave.cpp:471] Slave attributes: [  ]

I0408 15:11:00.967560  7892 slave.cpp:476] Slave hostname: slave1.openstacklocal

I0408 15:11:00.971304  7893 state.cpp:58] Recovering state from
'/tmp/mesos/meta'

*Failed to perform recovery: Incompatible slave info detected*.



Old slave info:

hostname: "*slave_public_IP_i_set*"

resources {

  name: "cpus"

  type: SCALAR

  scalar {

value: 1

  }

  role: "*"

}

resources {

  name: "mem"

  type: SCALAR

  scalar {

value: 920

  }

  role: "*"

}

resources {

  name: "disk"

  type: SCALAR

  scalar {

value: 5112

  }

  role: "*"

}

resources {

  name: "ports"

  type: RANGES

  ranges {

range {

  begin: 31000

  end: 32000

}

  }

  role: "*"

}

id {

  value: "ad490064-1a6e-415c-8536-daef0d8e3572-S7"

}

checkpoint: true

port: 5051