IBM Support

JR60667: KAFKA SERVICE OCCACIONALLY FAILS TO START ON AIX ENVIRONMENT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Kafka service occacionally fails to start on AIX environment.
    
    There are the following messages in kafka-server.log when the
    error occurs.
    -----
    2019-01-29 22:28:07,967 FATAL [main] [Kafka Server 1], Fatal
    error during KafkaServer startup. Prepare to shutdown
    java.lang.RuntimeException: A broker is already registered on
    the path /brokers/ids/1. This probably indicates that you either
    have configured a brokerid that is already in use, or else you
    have shutdown this broker and restarted it faster than the
    zookeeper timeout so it appears to be re-registering.
            at
    kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:305)
            at
    kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:291)
            at
    kafka.server.KafkaHealthcheck.register(KafkaHealthcheck.scala:70
    )
            at
    kafka.server.KafkaHealthcheck.startup(KafkaHealthcheck.scala:51)
            at
    kafka.server.KafkaServer.startup(KafkaServer.scala:244)
            at
    kafka.server.KafkaServerStartable.startup(KafkaServerStartable.s
    cala:37)
            at kafka.Kafka$.main(Kafka.scala:67)
            at kafka.Kafka.main(Kafka.scala)
    2019-01-29 22:28:07,972 INFO  [main] [Kafka Server 1], shutting
    down
    

Local fix

  • Add 'sleep 30' before 'stopsrc -s InfoSrvZookeeper 2>&1' in
    stop-aix-services.sh.
    
    if [ ! "${COMPONENTS#*zookeeper}" = "$COMPONENTS" ]; then
        sleep 30     <<---
        stopsrc -s InfoSrvZookeeper 2>&1
        sleep 5
    fi
    

Problem summary

  • Kafka is unable down properlz because yookeeper is alreadz shut
    down.
    

Problem conclusion

  • Before stopping the Yookeeper service a wait statement was added
    in order to give Kafka enough time during shut down to write its
    state to Zookeeper.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR60667

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-18

  • Closed date

    2019-03-04

  • Last modified date

    2019-03-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R850 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5"}]

Document Information

Modified date:
03 September 2021