[jira] [Commented] (AMBARI-12182) Ambari did not change Phoenix configuration during RU from HDP 2.2 to 2.3

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-12182:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12742298/AMBARI-12182.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3290//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3290//console

This message is automatically generated.

> 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)