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/06/30 22:41:04 UTC
[jira] [Reopened] (AMBARI-12182) Ambari did not change Phoenix
configuration during RU from HDP 2.2 to 2.3
[ https://issues.apache.org/jira/browse/AMBARI-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Mohanty reopened AMBARI-12182:
------------------------------------
Ambari upgrade did not set phoenix_sql_enabled to true.
> Ambari did not change Phoenix configuration during RU from HDP 2.2 to 2.3
> -------------------------------------------------------------------------
>
> Key: AMBARI-12182
> URL: https://issues.apache.org/jira/browse/AMBARI-12182
> 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
>
> Attachments: AMBARI-12182.2.patch, AMBARI-12182.patch
>
>
> When upgrading HDP-2.2 to HDP-2.3, there are a few configurations in hbase-site.xml needed to be changed by Ambari (see below). This particular bug was caused by Ambari using the old value for "hbase.region.server.rpc.scheduler.factory.class" from HDP-2.2 after upgrading. The upgrade process was blocked and was asked to downgrade in Ambari UI.
> {code}
> <property>
> <name>hbase.region.server.rpc.scheduler.factory.class</name>
> <value>org.apache.hadoop.hbase.ipc.PhoenixRpcSchedulerFactory</value>
> </property>
> <property>
> <name>hbase.rpc.controllerfactory.class</name>
> <value>org.apache.hadoop.hbase.ipc.controller.ServerRpcControllerFactory</value>
> </property>
> <property>
> <name>hbase.regionserver.wal.codec</name>
> <value>org.apache.hadoop.hbase.regionserver.wal.IndexedWALEditCodec</value>
> </property>
> <property>
> <name>fs.hdfs.impl</name>
> <value>org.apache.hadoop.hdfs.DistributedFileSystem</value>
> </property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)