[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Chen updated MESOS-4328:
Shepherd: Timothy Chen
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
>Assignee: AndyPang
> Labels: mesosphere
> Fix For: 0.27.0
>
> Attachments: docker.patch
>
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> {code}
> bug fix: we just like mesoscontainer in docker.cpp function cgroupsStatistics
> add the timestamp value set, more on patch,the result as flow
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.15dd3644-b902-11e5-ac40-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 192512,
> "timestamp": 1452585472.6926
> }
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Chen updated MESOS-4328:
Fix Version/s: 0.27.0
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
>Assignee: AndyPang
> Labels: mesosphere
> Fix For: 0.27.0
>
> Attachments: docker.patch
>
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> {code}
> bug fix: we just like mesoscontainer in docker.cpp function cgroupsStatistics
> add the timestamp value set, more on patch,the result as flow
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.15dd3644-b902-11e5-ac40-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 192512,
> "timestamp": 1452585472.6926
> }
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu updated MESOS-4328:
--
Labels: mesosphere (was: patch)
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: mesosphere
> Attachments: docker.patch
>
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> {code}
> bug fix: we just like mesoscontainer in docker.cpp function cgroupsStatistics
> add the timestamp value set, more on patch,the result as flow
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.15dd3644-b902-11e5-ac40-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 192512,
> "timestamp": 1452585472.6926
> }
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
{code}
bug fix: we just like mesoscontainer in docker.cpp function cgroupsStatistics
add the timestamp value set, more on patch,the result as flow
{code:title=statistics.json|borderStyle=solid}
[
{
"executor_id": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.15dd3644-b902-11e5-ac40-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.15dd3644-b902-11e5-ac40-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 192512,
"timestamp": 1452585472.6926
}
}
]
{code}
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
{code}
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
> Attachments: docker.patch
>
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> {code}
> bug fix: we just like mesoscontainer in docker.cpp function cgroupsStatistics
> add the timestamp value set, more on patch,the result as flow
> {code:title=statistics.json|borderStyle=solid}
> [
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Attachment: docker.patch
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
> Attachments: docker.patch
>
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
{code}
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:JavaScript}
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
{code}
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:JavaScript}
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
{code}
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:JavaScript}
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:JavaScript}
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:JavaScript}
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:JavaScript}
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:JavaScript}
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:JavaScript}
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
/monitor/statistics.json output format
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:JavaScript}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
/monitor/statistics.json output format
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
///monitor/statistics.json output format
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> /monitor/statistics.json output format
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
///monitor/statistics.json output format
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> ///monitor/statistics.json output format
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
{code:title=statistics.json|borderStyle=solid}
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
+[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]+
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> {code:title=statistics.json|borderStyle=solid}
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
+[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]+
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
*[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]*
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> +[
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]+
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
*[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]*
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]%
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> *[
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
!2016-01-12_111951.png!
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
!C:\Users\p00278970\Desktop\2016-01-12_111951.png!
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> %
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> !2016-01-12_111951.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]%
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
!2016-01-12_111951.png!
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> %[
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]%
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
!C:\Users\p00278970\Desktop\2016-01-12_111951.png!
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> %
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> !C:\Users\p00278970\Desktop\2016-01-12_111951.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
%
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> %
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
*
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
*
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
*
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
*
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
!
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
!
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> *
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> *
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
!
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
!
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
'''
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
'''
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> !
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> !
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[
https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-4328:
Description:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
'''
[
{
"executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"executor_name": "Command Executor (Task:
sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
"framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
"source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
"statistics": {
"cpus_limit": 1.1,
"cpus_system_time_secs": 0,
"cpus_user_time_secs": 0.02,
"mem_limit_bytes": 50331648,
"mem_rss_bytes": 200704
}
}
]
'''
was:
mesos 0.25.0 version if slave startup flags --containerizers=docker, using
docker container the rest api "/monitor/statistics.json" output have no
timestamp field,while if the mesoscontainer the output will have the timestamp
field.
So if we use docker container we maybe cann't calculate cpu utilization based
on timestamp, futhermore the "timestamp" is the required filed in
ResourceStatistics message.
> Docker container REST API /monitor/statistics.json output have no timestamp
> field
> --
>
> Key: MESOS-4328
> URL: https://issues.apache.org/jira/browse/MESOS-4328
> Project: Mesos
> Issue Type: Bug
> Components: docker
>Affects Versions: 0.25.0
> Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan
> 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
> Labels: patch
>
> mesos 0.25.0 version if slave startup flags --containerizers=docker, using
> docker container the rest api "/monitor/statistics.json" output have no
> timestamp field,while if the mesoscontainer the output will have the
> timestamp field.
> So if we use docker container we maybe cann't calculate cpu utilization based
> on timestamp, futhermore the "timestamp" is the required filed in
> ResourceStatistics message.
> '''
> [
> {
> "executor_id": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "executor_name": "Command Executor (Task:
> sleep.ecf0e700-b8da-11e5-95db-0242872c438f) (Command: sh -c 'sleep 3')",
> "framework_id": "cdb28c37-14c6-4877-a591-4eabbc6d84f2-",
> "source": "sleep.ecf0e700-b8da-11e5-95db-0242872c438f",
> "statistics": {
> "cpus_limit": 1.1,
> "cpus_system_time_secs": 0,
> "cpus_user_time_secs": 0.02,
> "mem_limit_bytes": 50331648,
> "mem_rss_bytes": 200704
> }
> }
> ]
> '''
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[ https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AndyPang updated MESOS-4328: Flags: Patch,Important (was: Important) Labels: patch (was: ) Description: mesos 0.25.0 version if slave startup flags --containerizers=docker, using docker container the rest api "/monitor/statistics.json" output have no timestamp field,while if the mesoscontainer the output will have the timestamp field. So if we use docker container we maybe cann't calculate cpu utilization based on timestamp, futhermore the "timestamp" is the required filed in ResourceStatistics message. was: mesos 0.25.0 version if slave startup flags --containerizers=docker, using docker container the rest api "/monitor/statistics.json" output have no timestamp field,while if the mesoscontainer the output will have the timestamp field. So if we use docker container we maybe cann't calculate cpu utilization based on timestamp, futhermore the "timestamp" is the required filed in ResourceStatistics message. > Docker container REST API /monitor/statistics.json output have no timestamp > field > -- > > Key: MESOS-4328 > URL: https://issues.apache.org/jira/browse/MESOS-4328 > Project: Mesos > Issue Type: Bug > Components: docker >Affects Versions: 0.25.0 > Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan > 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux >Reporter: AndyPang > Labels: patch > > mesos 0.25.0 version if slave startup flags --containerizers=docker, using > docker container the rest api "/monitor/statistics.json" output have no > timestamp field,while if the mesoscontainer the output will have the > timestamp field. > So if we use docker container we maybe cann't calculate cpu utilization based > on timestamp, futhermore the "timestamp" is the required filed in > ResourceStatistics message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4328) Docker container REST API /monitor/statistics.json output have no timestamp field
[ https://issues.apache.org/jira/browse/MESOS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] AndyPang updated MESOS-4328: Description: mesos 0.25.0 version if slave startup flags --containerizers=docker, using docker container the rest api "/monitor/statistics.json" output have no timestamp field,while if the mesoscontainer the output will have the timestamp field. So if we use docker container we maybe cann't calculate cpu utilization based on timestamp, futhermore the "timestamp" is the required filed in ResourceStatistics message. was:mesos 0.25.0 version if slave startup flags --containerizers=docker, using docker container the rest api "/monitor/statistics.json" output have no timestamp field,while if the mesoscontainer the output will have the timestamp field.So if we use docker container we maybe cann't calculate cpu utilization based on timestamp, futhermore the "timestamp" is the required filed in ResourceStatistics message. > Docker container REST API /monitor/statistics.json output have no timestamp > field > -- > > Key: MESOS-4328 > URL: https://issues.apache.org/jira/browse/MESOS-4328 > Project: Mesos > Issue Type: Bug > Components: docker >Affects Versions: 0.25.0 > Environment: Linux 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan > 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux >Reporter: AndyPang > > mesos 0.25.0 version if slave startup flags --containerizers=docker, using > docker container the rest api "/monitor/statistics.json" output have no > timestamp field,while if the mesoscontainer the output will have the > timestamp field. > So if we use docker container we maybe cann't calculate cpu utilization based > on timestamp, futhermore the "timestamp" is the required filed in > ResourceStatistics message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
