[
https://issues.apache.org/jira/browse/AMBARI-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191657#comment-14191657
]
Hadoop QA commented on AMBARI-8062:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12678450/AMBARI-8062_branch-1.6.1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/430//console
This message is automatically generated.
> 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
> 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)
