Contrail Database Kafka keep flapping afters delete controller SM provisioning

Bug #1543866 reported by Sarath
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Won't Fix
High
wenqing liang
R3.0
Won't Fix
High
wenqing liang
R3.0.2.x
Won't Fix
High
wenqing liang
R3.1
Won't Fix
High
wenqing liang
R3.2
Won't Fix
High
wenqing liang
Trunk
Won't Fix
High
wenqing liang

Bug Description

Thilak debugged the setup and looks the issue is due to "broker_id" mismatch aftermath of delete controller.
Per thilak analysis, this should be bug also on fab-provisioning.
This issue seen with 2711 build

root@a5d11e13:~#
root@a5d11e13:~# contrail-status
== Contrail Control ==
supervisor-control: active
contrail-control active
contrail-control-nodemgr active
contrail-dns active
contrail-named active

== Contrail Analytics ==
supervisor-analytics: active
contrail-alarm-gen active
contrail-analytics-api initializing (UvePartitions:UVE-Aggregation connection down)
contrail-analytics-nodemgr active
contrail-collector active
contrail-query-engine active
contrail-snmp-collector active
contrail-topology active

== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-config-nodemgr active
contrail-device-manager active
contrail-discovery:0 active
contrail-schema active
contrail-svc-monitor active
ifmap active

== Contrail Web UI ==
supervisor-webui: active
contrail-webui active
contrail-webui-middleware active

== Contrail Database ==
contrail-database: active
supervisor-database: active
contrail-database-nodemgr active
kafka initializing

== Contrail Support Services ==
supervisor-support-service: active
rabbitmq-server active

root@a5d11e13:~#

tail -f /var/log/kafka/server.log
[2016-02-09 16:02:54,352] FATAL Fatal error during KafkaServerStartable startup. Prepare to shutdown (kafka.server.KafkaServerStartable)
kafka.common.InconsistentBrokerIdException: Configured brokerId 1 doesn't match stored brokerId 2 in meta.properties
        at kafka.server.KafkaServer.getBrokerId(KafkaServer.scala:613)
        at kafka.server.KafkaServer.startup(KafkaServer.scala:177)
        at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:28)
        at kafka.Kafka$.main(Kafka.scala:69)
        at kafka.Kafka.main(Kafka.scala)
[2016-02-09 16:02:54,356] INFO shutting down (kafka.server.KafkaServer)
[2016-02-09 16:02:56,402] INFO KafkaConfig values:
        request.timeout.ms = 30000
        log.roll.hours = 168
        inter.broker.protocol.version = 0.9.0.X
        log.preallocate = false
        security.inter.broker.protocol = PLAINTEXT
        controller.socket.timeout.ms = 30000
        ssl.keymanager.algorithm = SunX509
        ssl.key.password = key_password
        log.cleaner.enable = true
        ssl.provider = null
        quota.consumer.bytes.per.second.overrides =
        num.recovery.threads.per.data.dir = 1
        background.threads = 10
        unclean.leader.election.enable = true
        quota.producer.bytes.per.second.overrides =
        replica.lag.time.max.ms = 10000
        auto.create.topics.enable = true
        zookeeper.sync.time.ms = 2000
        ssl.client.auth = none
        ssl.keystore.password = keystore_password
        log.cleaner.io.buffer.load.factor = 0.9
        offsets.topic.compression.codec = 0

Tags: ha
Revision history for this message
Sarath (nsarath) wrote :

-bash-4.1$
-bash-4.1$ hostname
centos-build02
-bash-4.1$
-bash-4.1$ pwd
/users/nsarath/PR/PR-1543866
-bash-4.1$
-bash-4.1$ ls -l
total 1449536
-rwxrwxrwx 1 nsarath test 1022801920 Feb 9 16:37 SMlog.tar*
-rwxrwxrwx 1 nsarath test 768000 Feb 9 16:37 SMRunlog.tar*
-rwxrwxrwx 1 nsarath test 454922240 Feb 9 16:36 target-log.tar*
-bash-4.1$

Revision history for this message
Abhay Joshi (abhayj) wrote :

Removed SM tag as bug does not seem related to SM.

tags: removed: server-manager
Jeba Paulaiyan (jebap)
tags: added: ha
Jeba Paulaiyan (jebap)
Changed in juniperopenstack:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.