You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2014/01/16 16:33:19 UTC
[jira] [Created] (AMBARI-4319) Task timeout should be a
configurable knob at the ambari-server
Dmitry Lysnichenko created AMBARI-4319:
------------------------------------------
Summary: Task timeout should be a configurable knob at the ambari-server
Key: AMBARI-4319
URL: https://issues.apache.org/jira/browse/AMBARI-4319
Project: Ambari
Issue Type: Improvement
Components: agent, controller, test
Affects Versions: 1.5.0
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 1.5.0
Task timeout is a configurable knob at the ambari-agent.
timeout_seconds = 600
This opens up the possibility of different timeout value at different agent instances as well as different value between the server and the agent. This can lead to state where server may have timed out the tasks but agent may not have. The other way is benign.
This config can be moved to the server and server can hand it off to the agent when agent registers. This also makes it easier to manage the timeout value.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)