Alejandro Fernandez created AMBARI-13918:
--------------------------------------------
Summary: Stack Upgrade: Kafka to call migration script when
upgrading across HDP 2.3.4.0
Key: AMBARI-13918
URL: https://issues.apache.org/jira/browse/AMBARI-13918
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.0, 2.1.3
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 2.2.0, 2.1.3
In HDP 2.3.4.0, the the structure of stored acls for Kafka in zookeeper has
changed. This means to support upgrade-to or downgrade-from HDP 2.3.4.0 we will
have to move these stored acls to new format or vice versa.
Ambari should make the following changes for upgrade/downgrade process of Kafka.
PreReq: Install bits side-by-side
Steps:
1) Stop all Kafka brokers
2) Call
bin/kafka-acls.sh --authorizer kafka.security.auth.SimpleAclAuthorizer
--authorizer-properties zookeeper.connect=localhost:2181 --upgradeAcls
or
bin/kafka-acls.sh --authorizer kafka.security.auth.SimpleAclAuthorizer
--authorizer-properties zookeeper.connect=localhost:2181 --downgradeAcls
3) Start all Kafka brokers.
Example Cases:
1) If upgrading from HDP 2.3.0.0 -> 2.3.2.0, we will still stop all Kafka
brokers since cannot distinguish the version in the single upgrade pack.
Customers may modify this behavior by editing upgrade-2.3.xml.
Because the 2.3.4.0 boundary is not crossed, we should not call the migration
script.
2) If upgrading from HDP 2.3.4.0->2.3.5.0, then we will stop all Kafka brokers
and not call the migration script since not crossing the boundary.
3) If upgrading from HDP 2.3.2.0->2.3.5.0, then we will stop all Kafka brokers
and call the migration script since crossing the boundary. On downgrade, we
should call the migration script again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
