[
https://issues.apache.org/jira/browse/AMBARI-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642630#comment-14642630
]
Hudson commented on AMBARI-12548:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3174 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3174/])
AMBARI-12548 Ambari Agent does not register / heartbeat if "df" command hangs
(dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=819ab1049fbe57bd12e94331e0823a5c153e7a78)
* ambari-server/src/test/python/custom_actions/TestCheckHost.py
* ambari-agent/src/test/python/ambari_agent/TestHardware.py
* ambari-agent/src/main/python/ambari_agent/Hardware.py
> Ambari Agent does not register / heartbeat if "df" command hangs
> ----------------------------------------------------------------
>
> Key: AMBARI-12548
> URL: https://issues.apache.org/jira/browse/AMBARI-12548
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.1.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12548.patch
>
>
> The agent executes the "df" command when it starts up.
> In rare scenarios, this command can hang (can even hanging for several days
> without any timeout). When this happens the agent won't move forward to the
> process of registration, etc.
> There's an ambari-server property called agent.check.mounts.timeout. This can
> be defined to force a timeout.
> However, we should always have a default timeout on the agent script side,
> even if this property is not defined to avoid a situation where the agent is
> completely hung.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
