Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 27 Jul 2015 09:34:04 +0000 (UTC)
From: "Dmytro Sen (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12849266.1437989499000.295322.1437989644526@Atlassian.JIRA>
In-Reply-To: <JIRA.12849266.1437989499000@Atlassian.JIRA>
References: <JIRA.12849266.1437989499000@Atlassian.JIRA>
 <JIRA.12849266.1437989499780@arcas>
Subject: [jira] [Updated] (AMBARI-12548) Ambari Agent does not register /
 heartbeat if "df" command hangs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen updated AMBARI-12548:
--------------------------------
    Attachment: AMBARI-12548.patch

> 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)