You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2015/08/26 22:48:59 UTC
[jira] [Updated] (AMBARI-8062) socket-timeout should be
configurable
[ https://issues.apache.org/jira/browse/AMBARI-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate Cole updated AMBARI-8062:
------------------------------
Fix Version/s: (was: 2.1.1)
2.1.2
> socket-timeout should be configurable
> -------------------------------------
>
> Key: AMBARI-8062
> URL: https://issues.apache.org/jira/browse/AMBARI-8062
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent
> Affects Versions: 1.6.1
> Environment: ambari-1.6.1
> Reporter: kyungwan nam
> Assignee: kyungwan nam
> Priority: Minor
> Fix For: 2.1.2
>
> Attachments: AMBARI-8062.patch, AMBARI-8062_branch-1.7.0.patch
>
>
> i've created a new stack which is include files of large size.
> socket timeout happens in the ambari-agent when i setup a cluster using my stack.
> default socket timeout is hardcoded in FileCache (10s).
> i think it looks better if socket_timeout is configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)