Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
0.21.1
-
None
-
Linux version 3.10.0-123.13.2.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.2 20140120 (Red Hat 4.8.2-16) (GCC) ) #1 SMP Thu Dec 18 14:09:13 UTC 2014
Description
I started a simple command line task via marathon. If I fetch state.json from the relevant slave, I get following result, where there is an empty executor_id. Could we have always an id for the executor?
{ "completed_tasks": [], "container": "9f4114ce-87b5-4640-ae5e-152eee140be3", "directory": "/hdd/mesos/slave/slaves/20150122-211400-234885292-5050-20977-S0/frameworks/20141119-101031-201330860-5050-3757-0000/executors/testtest.ca08dbeb-b05e-11e4-901a-56847afe9799/runs/9f4114ce-87b5-4640-ae5e-152eee140be3", "id": "testtest.ca08dbeb-b05e-11e4-901a-56847afe9799", "name": "Command Executor (Task: testtest.ca08dbeb-b05e-11e4-901a-56847afe9799) (Command: sh -c 'sleep 400')", "queued_tasks": [], "resources": { "cpus": 0.2, "disk": 0, "mem": 48, "ports": "[31029-31029]" }, "source": "testtest.ca08dbeb-b05e-11e4-901a-56847afe9799", "tasks": [ { "executor_id": "", "framework_id": "20141119-101031-201330860-5050-3757-0000", "id": "testtest.ca08dbeb-b05e-11e4-901a-56847afe9799", "name": "testtest", "resources": { "cpus": 0.1, "disk": 0, "mem": 16, "ports": "[31029-31029]" }, "slave_id": "20150122-211400-234885292-5050-20977-S0", "state": "TASK_RUNNING", "statuses": [ { "state": "TASK_RUNNING", "timestamp": 1423488189.20713 } ] } ] }
Attachments
Issue Links
- duplicates
-
MESOS-527 Command Executors do not have Executor IDs in the master.
- Reviewable
- is part of
-
MESOS-527 Command Executors do not have Executor IDs in the master.
- Reviewable
- is related to
-
MESOS-2743 Include ExecutorInfos for custom executors in master/state.json
- Resolved