You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Jay Buffington (JIRA)" <ji...@apache.org> on 2015/01/29 18:24:35 UTC
[jira] [Updated] (AURORA-1070) observer can't see pids running
inside docker containers
[ https://issues.apache.org/jira/browse/AURORA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Buffington updated AURORA-1070:
-----------------------------------
Description:
If you start a process with a task that has a container the observer is unable to collect stats on the pids running in the container. This results in warnings like this in your thermos.log:
{noformat}
W0129 16:54:10.284862 5743 process_collector_psutil.py:76] Error during process sampling: no process found with pid 247
{noformat}
I've heard the observer may be going away at some point, so perhaps this is moot. Do we have a jira tracking that work?
was:
If you start a process with a task that has a container the observer is unable to collect stats on the pids running in the container. This results in warnings like this in your thermos.log:
{{noformat}}
W0129 16:54:10.284862 5743 process_collector_psutil.py:76] Error during process sampling: no process found with pid 247
{{noformat}}
I've heard the observer may be going away at some point, so perhaps this is moot. Do we have a jira tracking that work?
> observer can't see pids running inside docker containers
> --------------------------------------------------------
>
> Key: AURORA-1070
> URL: https://issues.apache.org/jira/browse/AURORA-1070
> Project: Aurora
> Issue Type: Bug
> Components: Docker
> Reporter: Jay Buffington
>
> If you start a process with a task that has a container the observer is unable to collect stats on the pids running in the container. This results in warnings like this in your thermos.log:
> {noformat}
> W0129 16:54:10.284862 5743 process_collector_psutil.py:76] Error during process sampling: no process found with pid 247
> {noformat}
> I've heard the observer may be going away at some point, so perhaps this is moot. Do we have a jira tracking that work?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)