[jira] [Commented] (AMBARI-2088) Cluster installation times out at server side too fast

["Sumit Mohanty (JIRA)" <ji...@apache.org>]

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

Sumit Mohanty commented on AMBARI-2088:
---------------------------------------

Patch looks good. +1
                
> Cluster installation times out at server side too fast
> ------------------------------------------------------
>
>                 Key: AMBARI-2088
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2088
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.3.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-2088.patch
>
>
> Cluster installation fails on Datanode with task timeout aproximately in 5 minutes. It is not an UI issue, I've checked via API that server considers the request status to be TIMEDOUT, and agent continues running puppet manifests (each resulting with 0 return code). Agent logs does not contain watchdog messages. Our local internet connection is slower then Amazon internal network, and as a result installation takes more time (in my case, this issue reproduces almost every time when installing on a 2-node cluster). Clicking retry results in successful installation due to cached packages on previous attempt.
> We have different timeout values at agent and server (10 minutes and 5 minutes).
> /src/main/python/ambari_agent/PuppetExecutor.py:42
> PUPPET_TIMEOUT_SECONDS = 600
> com.google.inject.AbstractModule#bindConstant
> bindConstant().annotatedWith(Names.named("actionTimeout")).to(300000L);

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira