Hi,
I'm trying to write a Mesos framework that should create persistent
volumes and then start a Docker container that uses this. So far I was
able to dynamically reserve resources (cpu, memory and disk) and create
a persistent volume in the reserved disk space. I'm also able to launch
a Docker
y EMC - mesos-dvdi, which abstracts the volume
> creation. Please check this out and it should work with your scheduler …
>
>
> https://github.com/emccode/mesos-module-dvdi
>
> Thx
>
>
>
> On Thu, Jun 23, 2016 at 7:56 AM, Hendrik Haddorp
> <hendrik.hadd...@gmx.n
tainerizer and Docker Containerizer support integration
> with docker volume driver now, you can take a look
> at https://reviews.apache.org/r/36440/ for how to test docker volume
> driver with Docker Containerizer.
>
> Thanks,
>
> Guangya
>
> On Fri, Jun 24, 2016 at 2:5
but it works :-)
[1] https://issues.apache.org/jira/browse/MESOS-3413
[2]
https://github.com/arangodb/arangodb-mesos-framework/commit/98ccbdbaa5ae41f83b02ca42e7325746ad044099
p.s.: looks like jira is currently down ...
On 23/06/16 16:56, Hendrik Haddorp wrote:
> Hi,
>
> I'm trying to writ
Hi,
in mesos.proto [1] it states:
// Allowing arbitrary parameters to be passed to docker CLI.
// Note that anything passed to this field is not guaranteed
// to be supported moving forward, as we might move away from
// the docker CLI.
repeated Parameter parameters = 5;
Hi,
the Mesos code contains log statements using LOG(INFO) and VLOG(1), for
example. So far I found that Mesos is using the Google Logging Library.
Looking in the logs I only seem to be able to find output from VLOG
statements. What do I need to do to get the output from the LOG
statements? Where
--security-opt value
On 06/08/16 08:58, haosdent wrote:
> Hi, @Hendrik
>
> >which seems to be quite a restriction when looking at all the options
> the docker clihas
> May you provide any examples?
>
> On Sat, Aug 6, 2016 at 3:49 AM, Hendrik Haddorp
> <hendrik.hadd..
lue`. For
> example, you could use
>
> docker run --add-host=docker:10.180.0.1 --rm -it debian
>
> when use --add-host option which key is `add-host` and value is
> `docker:10.180.0.1`. Do you meet any problems when using them?
>
> On Sat, Aug 6, 2016 at 4:42 PM, Hendrik Haddorp
the environment variable GLOG_v
>
> And you can also set it through things like Spark. So if you want a
> lot of ZK chatter at the mesos level in your spark logs, add
>
> spark.executorEnv.GLOG_v=9
>
> to your spark context
>
> On Mon, Aug 8, 2016 at 2:53 PM
...
On 09/08/16 11:38, haosdent wrote:
> Hi, @Hendrik You could see INFO log when running Mesos Agent in
> default level. Some docker run logs may exist in the stdout/stderr of
> executor.
>
> On Tue, Aug 9, 2016 at 12:27 PM, Hendrik Haddorp
> <hendrik.hadd...@gmx.net <mailt
Hi,
I'm using Mesos 0.28.2 and my own framework, which uses dynamic
reservations. A task failed and shortly after that I received a resource
offers call that did not contain my reserved resources. I had expected
that the request would already contain my reserved resources that are
now not
?
If you are enabling GLOG_v=2 for mesos master, you will get some log
as "Framework xxx filtered agent for "
On Mon, Sep 26, 2016 at 2:47 PM, Hendrik Haddorp
<hendrik.hadd...@gmx.net <mailto:hendrik.hadd...@gmx.net>> wrote:
Hi,
I have three Mesos cluster
framework. You could get the
url of the agent from `Offer` as well.
On Tue, Oct 4, 2016 at 5:06 PM, Hendrik Haddorp
<hendrik.hadd...@gmx.net <mailto:hendrik.hadd...@gmx.net>> wrote:
Hi,
is there a way for a framework to determine what containerizers
are available on a s
Hi,
this sounds quite like a problem I had hit a few days ago. If you are
using the mesos native library you need to make sure that the LIBPROCESS
environment variables are set correctly. Otherwise the Mesos master can
not communicate back to your process, especially if you are not running
run the
mesos master and agent in docker using mini mesos
Sent from my iPad
On 27 Sep 2016, at 22:51, Hendrik Haddorp <hendrik.hadd...@gmx.net> wrote:
Hi,
this sounds quite like a problem I had hit a few days ago. If you are using the
mesos native library you need to mak
Hi,
I have three Mesos cluster test setups. On two my frameworks gets the
resource offers from all slaves in one "resourceOffers" call. In one
three node setup I do however sometimes get offers for all slaves but
most of the time I get first two offers and then the third in a separate
call.
if you do not set a filter
on an offer decline. Didn't quite expect that ;-)
On 26.09.2016 11:15, Hendrik Haddorp wrote:
I don't "own" the setup so that is not so easy. For now I'm keeping
the offers for a few seconds to get around it. If I get traces enabled
I'll let you know. I was fi
Hi,
when we take slaves down for maintenance, as described in
http://mesos.apache.org/documentation/latest/maintenance/, the slave
gets a new ID on start up. Why is that and can it be changed? We are
using Mesos 0.28.2. I'm so far only aware of the
slave_reregister_timeout. Our restart was
Hi,
it looks like on Mesos 0.28.2 Mesos stops receiving the logs once the
docker containerizer called "docker stop" and thus is missing logs one
might do in a graceful shutdown. I do at least see more logs when I do
"docker logs -f " compared to what I can see in Mesos. This is when
you
n increase logging on the framework (driver) and Mesos
master by setting GLOG_v=1 in the environment.
On Mon, Oct 31, 2016 at 12:42 AM, Hendrik Haddorp
<hendrik.hadd...@gmx.net <mailto:hendrik.hadd...@gmx.net>> wrote:
Hi,
I have a Mesos 0.28.2 system and generally thing
Hi,
what's the reason the the docker stop timeout is set to 0?
http://mesos.apache.org/documentation/latest/configuration/
--docker_stop_timeout=VALUEThe time docker daemon waits after
stopping a container before killing that container.
Hi,
I have a Mesos 0.28.2 system and generally things seem to run fine. The
"Outstanding Offers" normally shows nothing, which I believe is normal.
However at some point my framework gets disconnected for some odd
reason, might be due to some high load or so. A few seconds later I
receive a
Hi,
we did a migration from Mesos 0.28 to 1.3.0 and somehow it looks like
one framework "stole" resources another framework had reserved earlier.
Unfortunately I do not have any logs for the time frame so I'm not
certain what exactly happened. Currently we have one framework running
with a
Hi,
I build a small proxy for that. The required Mesos API is quite small so
I just created my own SchedulerDriver implementation and send then to a
proxy component that is running in a docker container. In there I can
easily have the native dependency. So a proxy scheduler is running in
this
"my-volume-227927c2-3266-412b-8572-92c5c93c051a" volume?
On Mon, Nov 27, 2017 at 7:59 AM, Hendrik Haddorp
<hendrik.hadd...@gmx.net <mailto:hendrik.hadd...@gmx.net>> wrote:
Hi,
I'm using persistent volumes directly on Mesos, without Marathon.
For that the schedul
Hi,
I'm using persistent volumes directly on Mesos, without Marathon. For
that the scheduler (like Marathon) has to first reserve disk space and
then create a persistent volume with that. The next resource offer
message then contain the volume in "disk" resource part of the offer.
Now you
uot;/home/xx/runtime/storm",
"mode": "RO"
}
],
"docker": {
"image": "xxx/storm-1.1.0",
"network": "HOST",
"portMappings": [],
"privileged": false,
"paramet
Hi,
I had been using Mesos 1.4.1 and now tried out a DC/OS setup (1.9.4) and
noticed that the env variable LIBPROCESS_IP was set. This broke my
scheduler (running as a docker container on Marathon). Things worked
fine again once I unset the variable in my startup script.
I'm now wondering
Hi,
I have a custom framework running on Mesos 1.8 using static reservation
so that resources are reserved for a specific role. For some time I had
two instances of my framework running, each using its own principal.
Each instance reserved resources and created persistent volumes. Then I
29 matches
Mail list logo
