ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14660) HistoryServer upgrade times out when /app-logs is too large
Date Wed, 24 Feb 2016 19:54:19 GMT

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

Hudson commented on AMBARI-14660:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #4382 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4382/])
AMBARI-14660. HistoryServer upgrade times out when /app-logs is too (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dfcea581e87f391199bc7bddf68a5675fc678303])
* 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, 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)

Mime
View raw message