Return-Path: 
 <dev-return-79291-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-dev-archive@www.apache.org
Delivered-To: apmail-ambari-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 0FE0E180D7
	for <apmail-ambari-dev-archive@www.apache.org>;
 Wed,  1 Jul 2015 01:42:05 +0000 (UTC)
Received: (qmail 38593 invoked by uid 500); 1 Jul 2015 01:42:04 -0000
Delivered-To: apmail-ambari-dev-archive@ambari.apache.org
Received: (qmail 38558 invoked by uid 500); 1 Jul 2015 01:42:04 -0000
Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ambari.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ambari.apache.org>
List-Post: <mailto:dev@ambari.apache.org>
List-Id: <dev.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list dev@ambari.apache.org
Received: (qmail 38544 invoked by uid 99); 1 Jul 2015 01:42:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 01:42:04 +0000
Date: Wed, 1 Jul 2015 01:42:04 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12841048.1435379915000.66066.1435714924597@Atlassian.JIRA>
In-Reply-To: <JIRA.12841048.1435379915000@Atlassian.JIRA>
References: <JIRA.12841048.1435379915000@Atlassian.JIRA>
 <JIRA.12841048.1435379915974@arcas>
Subject: [jira] [Commented] (AMBARI-12182) Ambari did not change Phoenix
 configuration during RU from HDP 2.2 to 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Hudson commented on AMBARI-12182:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #3043 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3043/])
AMBARI-12182. Ambari did not change Phoenix configuration during RU from HDP 2.2 to 2.3 - II (smohanty) (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7f4b94d995e35d582961cdb106c3624420197099)
* ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java


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