[
https://issues.apache.org/jira/browse/AMBARI-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604499#comment-14604499
]
Hudson commented on AMBARI-12182:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #135 (See
[https://builds.apache.org/job/Ambari-branch-2.1/135/])
AMBARI-12182. Ambari did not change Phoenix configuration during RU from HDP
2.2 to 2.3 (smohanty) (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f52c1b893c9d1c1ce7ec3ef1502ccf78e55b9a54)
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
> 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.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)