You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/06/01 17:06:59 UTC

[jira] [Commented] (AMBARI-16981) Update default ambari view read timeout to a larger value

    [ https://issues.apache.org/jira/browse/AMBARI-16981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310652#comment-15310652 ] 

Hadoop QA commented on AMBARI-16981:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12807405/AMBARI-16981_branch-2.4.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7105//console

This message is automatically generated.

> Update default ambari view read timeout to a larger value
> ---------------------------------------------------------
>
>                 Key: AMBARI-16981
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16981
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Pallav Kulshreshtha
>            Assignee: Pallav Kulshreshtha
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16981_branch-2.4.patch
>
>
>  it would be good to increase this timeout to handle cases where timeline server takes a long time to return.
> A value of atleast 30 seconds or 45 seconds would be a good start.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)