Late answer…
The setup example from
https://github.com/ControlSystemStudio/phoebus/blob/master/app/alarm/Readme.md still refers to Kafka 3.6 with Zookeeper. The alarm server and the CS-Studio desktop still build with kafka version 3.6.1.
In a first test, however, that seems to work fine with a kafka 4 installation.
Rough diffs to the Readme.md mentioned above:
Get kafka_2.13-4.0.0 instead of 2.13-3.6.1
There is no config/zookeeper.properties
In config/server.properties, there is no zookeeper.connection.timeout.ms,
but you should still update the “log.dirs” to be something other than /tmp
and set “auto.create.topics.enable=false”.
Starting kafka is now different, see
https://kafka.apache.org/documentation/#quickstart:
KAFKA_CLUSTER_ID="$(bin/kafka-storage.sh random-uuid)"
bin/kafka-storage.sh format --standalone -t $KAFKA_CLUSTER_ID -c config/server.properties
bin/kafka-server-start.sh config/server.properties
From then on, it’s the same:
sh create_alarm_topics.sh Accelerator
Start alarm server, start desktop, …
-Kay
From:
Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Paul Sichta via Tech-talk <tech-talk at aps.anl.gov>
Date: Wednesday, March 26, 2025 at 10:45 PM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] Phoebus alarm server with Kafka 4.0
I have been using Kafka 3. 7 on
our alarm server and we are building a new one on Rocky9. The (current) Kafka 4. 0. 0
no longer uses zookeeper, so our configuration in the Kafka server. properties file is a bit different. .
Will the Phoebus
I have been using Kafka 3.7 on our alarm server and we are building a new one on Rocky9. The (current) Kafka 4.0.0 no longer uses zookeeper, so our configuration in the Kafka server.properties file is a
bit different..
Will the Phoebus alarm server operate with Kafka 4, or should I stick with 3.x ? I ask because I'm having some issues with Phoebus connecting with the alarm server. The alarm log table does work for us.