[
https://issues.apache.org/jira/browse/AMBARI-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098046#comment-15098046
]
Hudson commented on AMBARI-14660:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #1001 (See
[https://builds.apache.org/job/Ambari-branch-2.1/1001/])
AMBARI-14660. HistoryServer upgrade times out when /app-logs is too (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2596e648f0804ae47ec7ef43d60e34119fee13c2])
*
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
Revert "AMBARI-14660. HistoryServer upgrade times out when /app-logs is
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f415e7e865186fe63580717eb2ea39512f0e6b8d])
*
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
> HistoryServer upgrade times out when /app-logs is too large
> -----------------------------------------------------------
>
> Key: AMBARI-14660
> URL: https://issues.apache.org/jira/browse/AMBARI-14660
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.2.1
>
> Attachments: AMBARI-14660.patch
>
>
> **Issue: Upgrading History Server timed out**
> * On investigation, it was noticed that we do some curl operations over
> WebHDFS on /app-logs HDFS folder.
> * Since the /app-logs folder was too large the script was taking too long
> (>1200 secs).
> * Retry of the upgrade step succeeded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
