[
https://issues.apache.org/jira/browse/UIMA-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-3739:
--------------------------------
Affects Version/s: 1.0.0-Ducc
Fix Version/s: (was: 1.0.0-Ducc)
1.1.0-Ducc
> Add more logging to Ducc Agent
> --------------------------------
>
> Key: UIMA-3739
> URL: https://issues.apache.org/jira/browse/UIMA-3739
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Affects Versions: 1.0.0-Ducc
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Minor
> Fix For: 1.1.0-Ducc
>
>
> Add additional logging to the Agent code to help diagnose why an Agent doesnt
> launch processes. This is rare but it does happen. The agent receives OR
> state, sees a new process and begins to launch it. The log shows that the
> last line logged in the launch sequence is just before the Agent tries to
> check if a cgroup with a given id exists.
> When the agent is in this state no processes are spawned.There is some
> evidence that the problem may be related to the OS problems. When the agent
> had trouble launching processes, it was observed that running a simple
> command like "rm" was taking a couple of minutes.
> The agent tries to determine if a cgroup exists using File.exists(). My
> hypothesis is that this call may block if the OS is in a bad state.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
