[
https://issues.apache.org/jira/browse/MESOS-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Lee updated MESOS-7894:
------------------------------
Description:
If you use the Docker container runtime, the 'Disk' 'Used' field never gets
populated in the Mesos UI (on the executor/task page).
Steps to Reproduce:
in DC/OS 1.9.2, deploy two apps:
{code:javascript}
{
"id": "/dummy-disk-docker",
"cmd": "dd if=/dev/zero of=$MESOS_SANDBOX/testfile bs=128M count=1; tail -f
/dev/null",
"instances": 1,
"cpus": 0.1,
"mem": 256,
"disk": 150,
"container": {
"type": "DOCKER",
"docker": {
"image": "alpine"
}
}
}
{code}
{code:javascript}
{
"id": "/dummy-disk-ucr",
"cmd": "dd if=/dev/zero of=$MESOS_SANDBOX/testfile bs=128M count=1; tail -f
/dev/null",
"instances": 1,
"cpus": 0.1,
"mem": 256,
"disk": 150,
"container": {
"type": "MESOS"
"docker": {
"image": "alpine"
}
}
}
{code}
Wait for them the deploy.
Then, navigate to the mesos UI, and go to the executor/task page for the two
tasks.
On the UCR task, eventually the "Used Disk" field should populate with 128 MB
(the size of the dummy file).
The same field on the Docker task will never get populated.
Both containers are writing to the same location on the agent filesystem
({{/var/lib/mesos/slave/slaves/<slave-id>/frameworks/<framework-id>/executors/<executor-id>/runs/latest}}),
but only one reports the data through the UI.
was:
If you use the Docker container runtime, the 'Disk' 'Used' field never gets
populated in the Mesos UI (on the executor/task page).
Steps to Reproduce:
in DC/OS 1.9.2, deploy two apps:
{code:javascript}
{
"id": "/dummy-disk-docker",
"cmd": "dd if=/dev/zero of=$MESOS_SANDBOX/testfile bs=128M count=1; tail -f
/dev/null",
"instances": 1,
"cpus": 0.1,
"mem": 256,
"disk": 150,
"container": {
"type": "DOCKER",
"docker": {
"image": "alpine"
}
}
}
{code}
{code:javascript}
{
"id": "/dummy-disk-ucr",
"cmd": "dd if=/dev/zero of=$MESOS_SANDBOX/testfile bs=128M count=1; tail -f
/dev/null",
"instances": 1,
"cpus": 0.1,
"mem": 256,
"disk": 150,
"container": {
"type": "MESOS"
"docker": {
"image": "alpine"
}
}
}
{code}
Wait for them the deploy.
Then, navigate to the mesos UI, and go to the executor/task page for the two
tasks.
On the UCR task, eventually the "Used Disk" field should populate with 128 MB
(the size of the dummy file).
The same field on the Docker task will never get populated.
Both containers are writing to the same location on the agent filesystem
(/var/lib/mesos/slave/slaves/<slave-id>/frameworks/<framework-id>/executors/<executor-id>/runs/latest,
but only one reports the data through the UI.
> Mesos Executor UI - Disk:Used Field isn't populated with Docker Container
> Runtime
> ---------------------------------------------------------------------------------
>
> Key: MESOS-7894
> URL: https://issues.apache.org/jira/browse/MESOS-7894
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: DC/OS 1.9.2 (CentOS 7.3, Docker 1.13.1, Mesos 1.2.2,
> Marathon 1.4.5)
> Reporter: Justin Lee
> Priority: Minor
> Attachments: UCR on left, Docker on right.png
>
>
> If you use the Docker container runtime, the 'Disk' 'Used' field never gets
> populated in the Mesos UI (on the executor/task page).
> Steps to Reproduce:
> in DC/OS 1.9.2, deploy two apps:
> {code:javascript}
> {
> "id": "/dummy-disk-docker",
> "cmd": "dd if=/dev/zero of=$MESOS_SANDBOX/testfile bs=128M count=1; tail -f
> /dev/null",
> "instances": 1,
> "cpus": 0.1,
> "mem": 256,
> "disk": 150,
> "container": {
> "type": "DOCKER",
> "docker": {
> "image": "alpine"
> }
> }
> }
> {code}
> {code:javascript}
> {
> "id": "/dummy-disk-ucr",
> "cmd": "dd if=/dev/zero of=$MESOS_SANDBOX/testfile bs=128M count=1; tail -f
> /dev/null",
> "instances": 1,
> "cpus": 0.1,
> "mem": 256,
> "disk": 150,
> "container": {
> "type": "MESOS"
> "docker": {
> "image": "alpine"
> }
> }
> }
> {code}
> Wait for them the deploy.
> Then, navigate to the mesos UI, and go to the executor/task page for the two
> tasks.
> On the UCR task, eventually the "Used Disk" field should populate with 128 MB
> (the size of the dummy file).
> The same field on the Docker task will never get populated.
> Both containers are writing to the same location on the agent filesystem
> ({{/var/lib/mesos/slave/slaves/<slave-id>/frameworks/<framework-id>/executors/<executor-id>/runs/latest}}),
> but only one reports the data through the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
