1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: [EXTERNAL] Phoebus alarm server with Kafka 4.0 |
From: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Paul Sichta <psichta at pppl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 5 May 2025 18:44:50 +0000 |
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 |