Useful attachments for a proactive case for Streams for Apache Kafka (formerly known as AMQ Streams) upgrade on RHEL

Environment

• Streams for Apache Kafka (version 2.7 and newer)
• AMQ Streams (until version 2.6)
• Red Hat Enterprise Linux

Issue

• Listing useful logs and data to attach to a proactive case when upgrading Streams for Apache Kafka/AMQ Streams on Red Hat Enterprise Linux

Resolution

Prerequisites

Having already read and applied what's written in the solution How to open a proactive case for patching or upgrading Streams for Apache Kafka (formerly known as AMQ Streams).

Data to attach

Here follow all the information and data useful to attach to the proactive case with related commands:

• JDK version used to run Streams for Apache Kafka/AMQ Streams

java -version

• Kafka configuration folder of both the current production environment, as well as the highest no-prod environment where the upgrade has been previously tested

zip -r streams_current_configs.zip ${PROD_KAFKA_DIR}/config
zip -r streams_replacing_configs.zip ${NO-PROD_KAFKA_DIR}/config

• Useful logs of both the current production environment (last 7 days are enough), as well as the highest no-prod environment where the upgrade has been previously tested

zip -r streams_prod_logs.zip ${PROD_KAFKA_LOGS_DIR}
zip -r streams_no-prod_logs.zip ${NO-PROD_KAFKA_LOGS_DIR}

• (Nice-to-have) Average/expected cluster throughput (measured in msg/s)
• (Nice-to-have) Current Storage setup
• (Nice-to-have) Client types (each one with related name/language and version)
• (Nice-to-have) Streams for Apache Kafka/AMQ Streams production cluster thread dumps, whose procedure has already been explained in a detailed solution

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.