Is there a one minute timeout on URI downloads or extractions?

[Rinaldo Digiorgio]

Hi,

I have several URI files configured in Marathon for download to the 
agent.  A mesos task starts and terminates consistently when trying to download 
the files.  I see the following message in the log.


I0503 20:24:38.330714  2756 slave.cpp:4322] Terminating executor 
‘'test.97c0bc52-11a7-11e6-99c8-56847afe9799' of framework 
e093b9e5-ad72-40e0-b686-9d41691141e5-1265' because it did not register within 
1mins

stderr shows some files being unzipped


Rinaldo

Re: Dynamic scaling of DCOS slave

[Joseph Wu]

You should be able to add as many agents as you like via manual
installation.  The list of agents you supply in the genconf is used for the
automated install processes.  For manual installation, the list of agents
is inconsequential (since you, the operator, are SSH-ing into each box).
See: https://dcos.io/docs/1.7/administration/installing/custom/advanced/

Also, please direct DC/OS questions towards us...@dcos.io for
better/more-complete answers.

On Tue, May 3, 2016 at 2:53 AM, Dhiraj Thakur 
wrote:

> Hi,
> Is there any way to scale up dcos slave without uninstalling existing
> setup?
> I have done installation through
> https://dcos.io/docs/1.7/administration/installing/custom/
>
> -Dhiraj
>

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Andrew Spyker]

resending as I wasn't on the (user) mailing list ...  sorry for the two
emails.  I hope this is useful.

This is from a pi 3 running a slave process connecting to a master not
running on pi.

pi@pi1:~ $ uname -a
Linux pi1 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
pi@pi1:~ $ file /sbin/init
/sbin/init: symbolic link to /lib/systemd/systemd
pi@pi1:~ $ file /lib/systemd/systemd
/lib/systemd/systemd: ELF 32-bit LSB shared object, ARM, EABI5 version 1
(SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for
GNU/Linux 2.6.32, BuildID[sha1]=2522b3d9033024e417036999161b98fa0b5d498f,
stripped
pi@pi1:~ $ export LD_LIBRARY_PATH=/usr/local/lib
pi@pi1:~ $ /usr/local/sbin/mesos-slave --master=
ec2-xx-xx-xx-xx.compute-1.amazonaws.com:7103
I0503 16:35:21.592422 12656 main.cpp:185] Build: 2016-04-29 03:52:47 by root
I0503 16:35:21.593188 12656 main.cpp:187] Version: 0.24.1
I0503 16:35:21.593456 12656 main.cpp:190] Git tag: 0.24.1
I0503 16:35:21.593680 12656 main.cpp:194] Git SHA:
44873806c2bb55da37e9adbece938274d8cd7c48
I0503 16:35:21.595311 12656 containerizer.cpp:143] Using isolation:
posix/cpu,posix/mem,filesystem/posix
I0503 16:35:21.626055 12656 main.cpp:272] Starting Mesos slave
I0503 16:35:21.630719 12656 slave.cpp:190] Slave started on
1)@xx.xx.xx.xx:5051
I0503 16:35:21.631299 12656 slave.cpp:191] 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_kill_orphans="true" --docker_remove_delay="6hrs"
--docker_socket="/var/run/docker.sock" --docker_stop_timeout="0ns"
--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" --initialize_driver_logging="true"
--isolation="posix/cpu,posix/mem" --launcher_dir="/usr/local/libexec/mesos"
--logbufsecs="0" --logging_level="INFO" --master="
ec2-xx-xx-xx-xx.compute-1.amazonaws.com:7103"
--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"
--resource_monitoring_interval="1secs" --revocable_cpu_low_priority="true"
--sandbox_directory="/mnt/mesos/sandbox" --strict="true"
--switch_user="true" --version="false" --work_dir="/tmp/mesos"
I0503 16:35:21.635468 12656 slave.cpp:354] Slave resources: cpus(*):4;
mem(*):462; disk(*):649; ports(*):[31000-32000]
I0503 16:35:21.636222 12656 slave.cpp:384] Slave hostname: pi1
I0503 16:35:21.636487 12656 slave.cpp:389] Slave checkpoint: true
I0503 16:35:21.669493 12657 state.cpp:54] Recovering state from
'/tmp/mesos/meta'
I0503 16:35:21.669802 12657 state.cpp:690] Failed to find resources file
'/tmp/mesos/meta/resources/resources.info'
I0503 16:35:21.670243 12657 state.cpp:97] Failed to find the latest slave
from '/tmp/mesos/meta'
I0503 16:35:21.673004 12658 status_update_manager.cpp:202] Recovering
status update manager
I0503 16:35:21.674284 12661 containerizer.cpp:379] Recovering containerizer
I0503 16:35:21.680462 12662 slave.cpp:4069] Finished recovery
I0503 16:35:21.684356 12657 slave.cpp:684] New master detected at
mas...@xx.xx.xx.xx:7103
I0503 16:35:21.684406 12660 status_update_manager.cpp:176] Pausing sending
status updates
I0503 16:35:21.686789 12657 slave.cpp:709] No credentials provided.
Attempting to register without authentication
I0503 16:35:21.687227 12657 slave.cpp:720] Detecting new master
^C
pi@pi1:~ $ file /usr/local/sbin/mesos-slave
/usr/local/sbin/mesos-slave: ELF 32-bit LSB executable, ARM, EABI5 version
1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-armhf.so.3,
for GNU/Linux 2.6.32,
BuildID[sha1]=0854662e0417291f2335990decb4b7be79724122, not stripped


On Tue, May 3, 2016 at 9:46 AM, Andrew Spyker  wrote:

> resending as I wasn't on the mailing list ...
>
> This is from a pi 3 running a slave process connecting to a master not
> running on pi.
>
> pi@pi1:~ $ uname -a
> Linux pi1 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
> pi@pi1:~ $ file /sbin/init
> /sbin/init: symbolic link to /lib/systemd/systemd
> pi@pi1:~ $ file /lib/systemd/systemd
> /lib/systemd/systemd: ELF 32-bit LSB shared object, ARM, EABI5 version 1
> (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for
> GNU/Linux 2.6.32, BuildID[sha1]=2522b3d9033024e417036999161b98fa0b5d498f,
> stripped
> pi@pi1:~ $ export LD_LIBRARY_PATH=/usr/local/lib
> pi@pi1:~ $ /usr/local/sbin/mesos-slave --master=
> 

Re: How to install marathon-lb

[Kamil Wokitajtis]

Did you try to run docker from command line?
You need to paste marathon and mesos logs, answer is probably there ;)

2016-05-03 10:54 GMT+02:00 Stefano Bianchi :

> Hi kamil
>
> I tried to replace that hostname with the one related to one random slave.
> And it does not work.
> I tried also to change the private IP od the marathon instance with the
> public, but i still have problem.
> I'm also running Mesos-DNS this should be a problem?
>
>
> 2016-05-02 21:52 GMT+02:00 Kamil Wokitajtis :
>
>> Did you try to run docker command from shell? Does it work for you?
>> Do you have also slave running on 131.154.96.27?
>> In my case entry was "constraints": [["hostname", "CLUSTER",
>> "master-1"]], because on host master-1 I have both master and slave running.
>> If you don't have slave running on 131.154.96.27, update this entry to
>> point to one of your slave hosts.
>>
>>
>> 2016-05-02 19:03 GMT+02:00 Stefano Bianchi :
>>
>>> Here it is:
>>>
>>> {
>>>
>>>   "id": "marathon-lb",
>>>
>>>   "volumes": [],
>>>
>>>   "cpus": 1,
>>>
>>>   "mem": 512,
>>>
>>>   "instances": 1,
>>>
>>>   "container": {
>>>
>>> "type": "DOCKER",
>>>
>>> "docker": {
>>>
>>> "image": "mesosphere/marathon-lb",
>>>
>>> "network": "HOST",
>>>
>>> "parameters": [
>>>
>>> { "key": "env", "value": "PORTS=9090" }
>>>
>>> ],
>>>
>>> "portMappings": [
>>>
>>>   {
>>>
>>>"containerPort": 80,
>>>
>>> "hostPort": 80,
>>>
>>> "servicePort": 10004,
>>>
>>> "protocol": "tcp"
>>>
>>>   },
>>>
>>>   {
>>>
>>>"containerPort": 9090,
>>>
>>> "hostPort": 9090,
>>>
>>> "servicePort": 10005,
>>>
>>> "protocol": "tcp"
>>>
>>>   }
>>>
>>> ]},
>>>
>>> "privileged": false
>>>
>>>   },
>>>
>>>   "args": [
>>>
>>>   "sse",
>>>
>>>   "--marathon", "http://192.168.100.54:8080;,
>>>
>>>   "--group", "external"
>>>
>>>   ],
>>>
>>>   "forcePullImage": true,
>>>
>>>   "constraints": [["hostname", "CLUSTER", "131.154.96.27"]]
>>>
>>> }
>>>
>>>
>>> where:
>>> 192.168.100.54 is the private IP there marathon is running.
>>>
>>> 131.154.96.27: is the hostname i set in /etc/mesos-master/hostname and
>>> /etc/mesos-master/ip files.
>>>
>>>
>>>
>>> 2016-05-02 17:20 GMT+02:00 Kamil Wokitajtis :
>>>
 Please paste your modified marathon-lb.json file.
 Can you see any error messages in the marathon and mesos logs ?
 We are mapping ports 80, 9090,10004,10005, those need to be open.

 Docker command is as follows:

 docker run --privileged -e PORTS=9090 --net=host -p 80:80 -p 9090:9090
 mesosphere/marathon-lb sse --marathon http://192.168.33.20:8080
 --group "external"

 2016-05-02 17:07 GMT+02:00 Stefano Bianchi :

> Can you please tell me which is the correspondent marathon-lb.json
> docker command?
>
> 2016-05-02 16:55 GMT+02:00 Stefano Bianchi :
>
>> All those ports must be open? Because i am on openstack environment
>> and i need to know if there is something to open
>>
>> 2016-05-02 15:52 GMT+02:00 Stefano Bianchi :
>>
>>> i changed all but i see waiting app.
>>>
>>> 2016-05-02 15:26 GMT+02:00 Kamil Wokitajtis :
>>>
 I am using private docker registry (
 https://docs.docker.com/registry/).
 In my case I can pull image from local repository installed on node
 master-1 (master-1:5000/marathon-lb):
  "image": "master-1:5000/marathon-lb"

 If you don't have private registry, you have to pull image from the
 docker hub (mesosphere/marathon-lb):
  "image": "mesosphere/marathon-lb"

 Basically, for many reasons I want all my images to be hosted
 locally.



 2016-05-02 15:10 GMT+02:00 Stefano Bianchi :

> Thanks your your answer.
> I understood what you are telling me, just a thing, what you mean
> with docker registry?
>
> 2016-05-02 13:31 GMT+02:00 Kamil Wokitajtis 
> :
>
>> Hi,
>>
>> Fastest way is to run marathon-lb docker image.
>> You have to update marathon-lb.json code below with yours (or
>> public) docker registry, IPs and hostnames.
>> When you add application to marathon and you want it to be load
>> balanced via marathon-lb,
>> you have to add labels section eg.:
>>
>>  "labels": {
>> "HAPROXY_GROUP":"external",
>> "HAPROXY_0_VHOST":"service.mesosphere.com"
>>   }
>>
>>
>> Reading documentation on github was enough for me, specially
>> "issues" tab ;)
>> 

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Tomek Janiszewski]

Current master version should build on Pi3 but there still could be a
problem with leveldb.

wt., 3.05.2016 o 16:40 użytkownik Andreas Fritzler <
andreas.fritz...@gmail.com> napisał:

> Did anybody try to build and run Mesos on a Raspberry Pi3? Will that work
> out of the box (due to the 64bit ARM)?
>
> On Sat, Apr 30, 2016 at 5:54 AM, haosdent  wrote:
>
>> >The master has problem running with this build on the Pi
>> You need launch master with `--registry=in_memory`, replicated_log with
>> leveldb has problem in Mesos master.
>>
>> On Sat, Apr 30, 2016 at 4:09 AM, Sharma Podila 
>> wrote:
>>
>> > Fyi- Things are progressing, we have a build on Pi. The agent was able
>> to
>> > come up and register with a master running on a regular Linux server.
>> >
>> > https://twitter.com/aspyker/status/725923864031559681
>> >
>> > The master has problem running with this build on the Pi, but, that
>> isn't
>> > a goal for us. We are running Mesos 0.24.1 for now. We'll document our
>> > build steps, etc. here soon.
>> >
>> >
>> >
>> > On Mon, Apr 25, 2016 at 10:21 AM, Sharma Podila 
>> > wrote:
>> >
>> >> This is for an internal hackday project, not for a production setup.
>> >>
>> >>
>> >> On Mon, Apr 25, 2016 at 1:05 AM, Aaron Carey  wrote:
>> >>
>> >>> Out of curiosity... is this for fun or production workloads? I'd be
>> >>> curious to hear about raspis being used in production!
>> >>>
>> >>> --
>> >>>
>> >>> Aaron Carey
>> >>> Production Engineer - Cloud Pipeline
>> >>> Industrial Light & Magic
>> >>> London
>> >>> 020 3751 9150
>> >>>
>> >>> --
>> >>> *From:* Sharma Podila [spod...@netflix.com]
>> >>> *Sent:* 22 April 2016 17:53
>> >>> *To:* user@mesos.apache.org; dev
>> >>> *Subject:* Running Mesos agent on ARM (Raspberry Pi)?
>> >>>
>> >>> We are working on a hack to run Mesos agents on Raspberry Pi and are
>> >>> wondering if anyone here has done that before. From the Google search
>> >>> results we looked at so far, it seems like it has been compiled, but
>> we
>> >>> haven't seen an indication that anyone has run it and launched tasks
>> on
>> >>> them. And does it sound right that it might take 4 hours or so to
>> compile?
>> >>>
>> >>> We are looking to run just the agents. The master will be on a regular
>> >>> Ubuntu laptop or a server.
>> >>>
>> >>> Appreciate any pointers.
>> >>>
>> >>>
>> >>>
>> >>
>> >
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Andreas Fritzler]

Did anybody try to build and run Mesos on a Raspberry Pi3? Will that work
out of the box (due to the 64bit ARM)?

On Sat, Apr 30, 2016 at 5:54 AM, haosdent  wrote:

> >The master has problem running with this build on the Pi
> You need launch master with `--registry=in_memory`, replicated_log with
> leveldb has problem in Mesos master.
>
> On Sat, Apr 30, 2016 at 4:09 AM, Sharma Podila 
> wrote:
>
> > Fyi- Things are progressing, we have a build on Pi. The agent was able to
> > come up and register with a master running on a regular Linux server.
> >
> > https://twitter.com/aspyker/status/725923864031559681
> >
> > The master has problem running with this build on the Pi, but, that isn't
> > a goal for us. We are running Mesos 0.24.1 for now. We'll document our
> > build steps, etc. here soon.
> >
> >
> >
> > On Mon, Apr 25, 2016 at 10:21 AM, Sharma Podila 
> > wrote:
> >
> >> This is for an internal hackday project, not for a production setup.
> >>
> >>
> >> On Mon, Apr 25, 2016 at 1:05 AM, Aaron Carey  wrote:
> >>
> >>> Out of curiosity... is this for fun or production workloads? I'd be
> >>> curious to hear about raspis being used in production!
> >>>
> >>> --
> >>>
> >>> Aaron Carey
> >>> Production Engineer - Cloud Pipeline
> >>> Industrial Light & Magic
> >>> London
> >>> 020 3751 9150
> >>>
> >>> --
> >>> *From:* Sharma Podila [spod...@netflix.com]
> >>> *Sent:* 22 April 2016 17:53
> >>> *To:* user@mesos.apache.org; dev
> >>> *Subject:* Running Mesos agent on ARM (Raspberry Pi)?
> >>>
> >>> We are working on a hack to run Mesos agents on Raspberry Pi and are
> >>> wondering if anyone here has done that before. From the Google search
> >>> results we looked at so far, it seems like it has been compiled, but we
> >>> haven't seen an indication that anyone has run it and launched tasks on
> >>> them. And does it sound right that it might take 4 hours or so to
> compile?
> >>>
> >>> We are looking to run just the agents. The master will be on a regular
> >>> Ubuntu laptop or a server.
> >>>
> >>> Appreciate any pointers.
> >>>
> >>>
> >>>
> >>
> >
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: How to add other file systems to an agent

[Rinaldo Digiorgio]

> On May 3, 2016, at 7:31 AM, Dick Davies  wrote:
> 
> I'd imagine it's reporting whatever partition the --work-dir argument
> on the slave is set to (sandboxes live under that directory).
Thanks


I see that there is support for attaching storage:  
http://mesos.apache.org/documentation/latest/persistent-volume/ 






> On 3 May 2016 at 12:21, Rinaldo Digiorgio  wrote:
>> Hi,
>> 
>>I have a configuration with a root file system and other file 
>> systems. When I start an agent, the agent only reports the disk on the root 
>> file system.  Is there a way to specify a list of file systems to include as 
>> resources of the agent when it starts? I checked the agent options.
>> 
>> 
>> Rinaldo

Re: How to add other file systems to an agent

[Dick Davies]

I'd imagine it's reporting whatever partition the --work-dir argument
on the slave is set to (sandboxes live under that directory).

On 3 May 2016 at 12:21, Rinaldo Digiorgio  wrote:
> Hi,
>
> I have a configuration with a root file system and other file 
> systems. When I start an agent, the agent only reports the disk on the root 
> file system.  Is there a way to specify a list of file systems to include as 
> resources of the agent when it starts? I checked the agent options.
>
>
> Rinaldo

How to add other file systems to an agent

[Rinaldo Digiorgio]

Hi,

I have a configuration with a root file system and other file systems. 
When I start an agent, the agent only reports the disk on the root file system. 
 Is there a way to specify a list of file systems to include as resources of 
the agent when it starts? I checked the agent options.


Rinaldo

Dynamic scaling of DCOS slave

[Dhiraj Thakur]

Hi,
Is there any way to scale up dcos slave without uninstalling existing setup?
I have done installation through 
https://dcos.io/docs/1.7/administration/installing/custom/

-Dhiraj

Re: How to install marathon-lb

[Stefano Bianchi]

Hi kamil

I tried to replace that hostname with the one related to one random slave.
And it does not work.
I tried also to change the private IP od the marathon instance with the
public, but i still have problem.
I'm also running Mesos-DNS this should be a problem?


2016-05-02 21:52 GMT+02:00 Kamil Wokitajtis :

> Did you try to run docker command from shell? Does it work for you?
> Do you have also slave running on 131.154.96.27?
> In my case entry was "constraints": [["hostname", "CLUSTER",
> "master-1"]], because on host master-1 I have both master and slave running.
> If you don't have slave running on 131.154.96.27, update this entry to
> point to one of your slave hosts.
>
>
> 2016-05-02 19:03 GMT+02:00 Stefano Bianchi :
>
>> Here it is:
>>
>> {
>>
>>   "id": "marathon-lb",
>>
>>   "volumes": [],
>>
>>   "cpus": 1,
>>
>>   "mem": 512,
>>
>>   "instances": 1,
>>
>>   "container": {
>>
>> "type": "DOCKER",
>>
>> "docker": {
>>
>> "image": "mesosphere/marathon-lb",
>>
>> "network": "HOST",
>>
>> "parameters": [
>>
>> { "key": "env", "value": "PORTS=9090" }
>>
>> ],
>>
>> "portMappings": [
>>
>>   {
>>
>>"containerPort": 80,
>>
>> "hostPort": 80,
>>
>> "servicePort": 10004,
>>
>> "protocol": "tcp"
>>
>>   },
>>
>>   {
>>
>>"containerPort": 9090,
>>
>> "hostPort": 9090,
>>
>> "servicePort": 10005,
>>
>> "protocol": "tcp"
>>
>>   }
>>
>> ]},
>>
>> "privileged": false
>>
>>   },
>>
>>   "args": [
>>
>>   "sse",
>>
>>   "--marathon", "http://192.168.100.54:8080;,
>>
>>   "--group", "external"
>>
>>   ],
>>
>>   "forcePullImage": true,
>>
>>   "constraints": [["hostname", "CLUSTER", "131.154.96.27"]]
>>
>> }
>>
>>
>> where:
>> 192.168.100.54 is the private IP there marathon is running.
>>
>> 131.154.96.27: is the hostname i set in /etc/mesos-master/hostname and
>> /etc/mesos-master/ip files.
>>
>>
>>
>> 2016-05-02 17:20 GMT+02:00 Kamil Wokitajtis :
>>
>>> Please paste your modified marathon-lb.json file.
>>> Can you see any error messages in the marathon and mesos logs ?
>>> We are mapping ports 80, 9090,10004,10005, those need to be open.
>>>
>>> Docker command is as follows:
>>>
>>> docker run --privileged -e PORTS=9090 --net=host -p 80:80 -p 9090:9090
>>> mesosphere/marathon-lb sse --marathon http://192.168.33.20:8080 --group
>>> "external"
>>>
>>> 2016-05-02 17:07 GMT+02:00 Stefano Bianchi :
>>>
 Can you please tell me which is the correspondent marathon-lb.json
 docker command?

 2016-05-02 16:55 GMT+02:00 Stefano Bianchi :

> All those ports must be open? Because i am on openstack environment
> and i need to know if there is something to open
>
> 2016-05-02 15:52 GMT+02:00 Stefano Bianchi :
>
>> i changed all but i see waiting app.
>>
>> 2016-05-02 15:26 GMT+02:00 Kamil Wokitajtis :
>>
>>> I am using private docker registry (
>>> https://docs.docker.com/registry/).
>>> In my case I can pull image from local repository installed on node
>>> master-1 (master-1:5000/marathon-lb):
>>>  "image": "master-1:5000/marathon-lb"
>>>
>>> If you don't have private registry, you have to pull image from the
>>> docker hub (mesosphere/marathon-lb):
>>>  "image": "mesosphere/marathon-lb"
>>>
>>> Basically, for many reasons I want all my images to be hosted
>>> locally.
>>>
>>>
>>>
>>> 2016-05-02 15:10 GMT+02:00 Stefano Bianchi :
>>>
 Thanks your your answer.
 I understood what you are telling me, just a thing, what you mean
 with docker registry?

 2016-05-02 13:31 GMT+02:00 Kamil Wokitajtis :

> Hi,
>
> Fastest way is to run marathon-lb docker image.
> You have to update marathon-lb.json code below with yours (or
> public) docker registry, IPs and hostnames.
> When you add application to marathon and you want it to be load
> balanced via marathon-lb,
> you have to add labels section eg.:
>
>  "labels": {
> "HAPROXY_GROUP":"external",
> "HAPROXY_0_VHOST":"service.mesosphere.com"
>   }
>
>
> Reading documentation on github was enough for me, specially
> "issues" tab ;)
> https://github.com/mesosphere/marathon-lb
>
>
> Below code works for me, but I think you can change "network" mode
> from BRIDGE to HOST and remove line : { "key": "net", "value": "host" 
> }.
>
> marathon-lb.json:
>
> {
>   "id": "marathon-lb",
>   "volumes": [],
>   "cpus": 0.5,
>   "mem": 

Re: How to use a complete host

[Staffan Larsen]

Instead of custom attributes to indicate the total resources available, you 
could use the /state endpoint on the agent to find out how much resources it 
has. Somewhat of a hack, but should work.

Thanks,
/Staffan

> On 2 maj 2016, at 23:43, Sharma Podila  wrote:
> 
> 
> This can't be achieved with the offer model as it stands today, unless you 
> have only a single framework in the cluster. There is no visibility into what 
> other resources are available on the agent which weren't offered to your 
> framework. 
> 
> However, for the short term, you can use a hack to put in custom attributes 
> that indicate the total amount of resources available on the agent. So, when 
> you get the offer, you can verify if you got the offer for the entire agent's 
> resources. 
> 
> Mesos-4138 is interesting, as Jeff pointed out.
> 
> 
> 
> 
> 
> On Mon, May 2, 2016 at 11:07 AM, haosdent  > wrote:
> It sounds like you could reserve resources by a role in that machine. And 
> then your framework launched by that role.
> 
> On Tue, May 3, 2016 at 1:57 AM, Christoph Heer  > wrote:
> Hi everyone,
> 
> sometimes in my Mesos use-case it's required to ensure that my own framework 
> is able to schedule a task which consume all resources of a machine.
> 
> Do you have some advises how to implement such a scheduler. Is there another 
> scheduler which already implemented something similar?
> 
> Thank you and best regards
> Christoph
> 
> 
> 
> -- 
> Best Regards,
> Haosdent Huang
>