You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "kyungwan nam (JIRA)" <ji...@apache.org> on 2014/11/02 06:25:33 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 ]

kyungwan nam updated AMBARI-8062:
---------------------------------
    Fix Version/s: 1.7.0

> 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: 1.7.0
>
>         Attachments: AMBARI-8062_branch-1.6.1.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)