You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2015/10/06 19:18:28 UTC
[jira] [Updated] (UIMA-4637) DUCC Agent should test if CPU control
is enabled on startup
[ https://issues.apache.org/jira/browse/UIMA-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-4637:
--------------------------------
Description:
Extend agent cgroup sanity check on startup to include a test for existence of CPU control. Users my forget to add cpu in their cgconfig.conf and start cgroups with no CPU control. The agent should call cgset and disable cgroups on failure.
Agent should keep the state of cgroup in memory and log it at some interval to make sure this info is not lost. Currently the agent logs the state of cgroups (enabled/disabled) at startup only. When agent logs roll over this is lost. Modify agent node metrics logic to dump the cgroup state at regular intervals.
was:
Extend agent cgroup sanity check to include a test for existence of CPU control. Users my forget to add cpu in their cgconfig.conf and start cgroups with no CPU control. The agent should call cgset and disable cgroups on failure.
Agent should keep the state of cgroup in memory and log it at some interval to make sure this info is not lost. Currently the agent logs the state of cgroups (enabled/disabled) at startup only. When agent logs roll over this is lost. Modify agent node metrics logic to dump the cgroup state at regular intervals.
> DUCC Agent should test if CPU control is enabled on startup
> -----------------------------------------------------------
>
> Key: UIMA-4637
> URL: https://issues.apache.org/jira/browse/UIMA-4637
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.1.0-Ducc
>
>
> Extend agent cgroup sanity check on startup to include a test for existence of CPU control. Users my forget to add cpu in their cgconfig.conf and start cgroups with no CPU control. The agent should call cgset and disable cgroups on failure.
> Agent should keep the state of cgroup in memory and log it at some interval to make sure this info is not lost. Currently the agent logs the state of cgroups (enabled/disabled) at startup only. When agent logs roll over this is lost. Modify agent node metrics logic to dump the cgroup state at regular intervals.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)