I am cross posting this to mesos-users, hoping someone has came accros
this issue, and can help me resolve this issue I have. There are several
JIRA issues open with similar symptoms.
All of a sudden I having problems with marathon ui getting stuck at
'loading' and end points like http://m01
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 wrote:
Hello,
I figured this issue. I want to share my findings so new users do not make the
same mistakes:
1. Make sure your /etc/hosts resolves the name to the master to a routable
IP. Mine was pointing to localhost. So I overrode /etc/mesos-master/ip. Do the
same on /etc/mesos/zk for the Zooke
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 schedu
json files and the framework info son as well as the logs from master and agent.Thanks and best regards,Ben
framework.json
Description: application/json
mesos-master.mp-weizenbaum.iais.fraunhofer.de.root.log.INFO.20200607-131745.54624
Description: Binary data
mesos-master.mp-weizenbaum.iais
6 matches
Mail list logo