ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-11640) During initial Stack Install, tarballs will not be copied to HDFS because the current_version is not yet known
Date Thu, 04 Jun 2015 00:22:38 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Fernandez updated AMBARI-11640:
-----------------------------------------
    Attachment:     (was: AMBARI-11640.patch)

> During initial Stack Install, tarballs will not be copied to HDFS because the current_version
is not yet known
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11640
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11640
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11640.patch
>
>
> During Install of services, Ambari doesn't yet know about the current_version, so it
doesn't get passed to command-###.json, for this reason, the copying of tarballs fails.
> The workaround is to start all services so that the CURRENT version exists, and then
rerun a HiveServer2 Start, Spark History Server2, or Tez Service Check.
> The fix will be to detect if params.current_version is None, and if so, call hdp-select
versions, and use the value if only one version number is reported.
> Also, HiveServer2 Start needs to copy the tez tarball.



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

Mime
View raw message