Turns out I had to configure the framework I desire to use to do exactly what
the mess-execute command did, adding GPU_RESOURCES to the capability list. Now
resources are offered to the framework and tasks are run. :)
Thanks,
Ben
> On 7. Jun 2020, at 15:01, Benjamin Wulff wrote:
>
> Hi all,
Hi all,
a correction:
I saw the correct output of nvidia-smi in the stdout file in the tasks work dir
on the agent (that was the piece I didn’t get, reading helps!).
So I have to see why the framework doesn’t receive any offers.
Thanks,
Ben
> On 7. Jun 2020, at 15:01, Benjamin Wulff
Hi all,I found the gnu-support site in the docs (1) and tried the following command:# mesos-execute --master=129.26.78.161:5050 --name=gpu-test --command="nvidia-smi" --framework_capabilities="GPU_RESOURCES" --resources="gpus:1”..and that gave the following output:I0607 14:57:41.897706 56361
Hi Benjamin,I can't quite tell from the log snippet you provided. Assuming this is the only scheduler registered, it should receive offers for all the agents for the scheduler's roles (in this case, should just be the '*' role).The framework I was talking about is the only framework in place. I
Don't worry about that "Ignoring" message on the agent. When the framework
information is updated, the master broadcasts it to the agents, and in this
case the agent doesn't know about the framework since it has no tasks for
it, and so it ignores the updated information.
I can't quite tell from
So with logging_level set to INFO (and master and slave restarted) I noticed in
/var/log/mesos.INFO on the agent the following line:
I0606 13:46:41.393455 206117 slave.cpp:4222] Ignoring info update for framework
2777de92-bc91-4e48-9960-bbab05694665- because it does not exist
That is
You already put these on debug?
[@ ]# cat /etc/mesos-master/logging_level
WARNING
[@ ]# cat /etc/mesos-slave/logging_level
WARNING
-Original Message-
From: Benjamin Wulff [mailto:benjamin.wulff...@ieee.org]
Sent: zaterdag 6 juni 2020 13:36
To: user@mesos.apache.org
Subject: No
7 matches
Mail list logo