You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/11/24 02:02:11 UTC
[jira] [Commented] (AMBARI-14027) Stack Upgrade: Kafka Broker error
finding property zookeeper.connect during upgrade from HDP 2.3.0 -> 2.3.M20
[ https://issues.apache.org/jira/browse/AMBARI-14027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023517#comment-15023517 ]
Hadoop QA commented on AMBARI-14027:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12773936/AMBARI-14027.trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4376//console
This message is automatically generated.
> Stack Upgrade: Kafka Broker error finding property zookeeper.connect during upgrade from HDP 2.3.0 -> 2.3.M20
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14027
> URL: https://issues.apache.org/jira/browse/AMBARI-14027
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.3
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-14027.trunk.patch
>
>
> * Ambari 2.2 rpm 324
> * HDP 2.3.0.0-2557
> * Installed HDFS, MR, YARN, ZK, Kafka
> * Added NameNode HA
> * Installed repo for HDP 2.3.4.0-3262 and distributed bits
> * Installed repo for HDP 2.3.4.0-3278 and distributed bits
> * Started Express Upgrade to 2.3.4.0-3262
> Failed on Kafka,
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py", line 101, in <module>
> KafkaBroker().execute()
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 218, in execute
> method(env)
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 497, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py", line 68, in pre_upgrade_restart
> upgrade.run_migration(env, upgrade_type)
> File "/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/upgrade.py", line 65, in run_migration
> raise Fail("Could not retrieve Zookeeper Port number for localhost from property kafka-broker/zookeeper.connect")
> resource_management.core.exceptions.Fail: Could not retrieve Zookeeper Port number for localhost from property kafka-broker/zookeeper.connect
> {code}
> This needs to be ran on a kerberized cluster only, and should use the full zookeeper.connect property now that the most recent Kafka builds support it (before they only accepted a single value, now they take a list of hosts with port numbers).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)