You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2015/07/07 21:26:04 UTC
[jira] [Commented] (AMBARI-12318) Phoenix rolling upgrade should
not expect phoenix specific configs
[ https://issues.apache.org/jira/browse/AMBARI-12318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617220#comment-14617220 ]
Sumit Mohanty commented on AMBARI-12318:
----------------------------------------
Phoenix rolling upgrade should not expect phoenix specific configs as phoenix uses hbase config
> Phoenix rolling upgrade should not expect phoenix specific configs
> ------------------------------------------------------------------
>
> Key: AMBARI-12318
> URL: https://issues.apache.org/jira/browse/AMBARI-12318
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.1.0
>
>
> conf-select set-conf-dir failed during RU because there are no /usr/hdp/2.3.0.0-2529/phoenix/conf and looks like conf-select create was never executed for a Phoenix component.
> {noformat}
> resource_management.core.exceptions.Fail: Execution of 'conf-select set-conf-dir --package phoenix --stack-version 2.3.0.0-2529 --conf-version 0' returned 1. /usr/hdp/2.3.0.0-2529/phoenix/conf does not exist
> {noformat}
> Phoenix package is distributed without conf folder, so during initial install conf-select create was skipped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)