Skip to content

Commit 55ce465

Browse files
authored
Merge pull request #2285 from ControlSystemStudio/alarm_doc
Alarm doc: Use bootstrap-server ...
2 parents a17585d + 61758b1 commit 55ce465

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

app/alarm/Readme.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -48,9 +48,9 @@ Similarly, change the directory setting in `server.properties`
4848
Kafka depends on Zookeeper. By default, Kafka will quit if it cannot connect to Zookeeper within 6 seconds.
4949
When the Linux host boots up, this may not be long enough to allow Zookeeper to start.
5050

51-
# Timeout in ms for connecting to zookeeper defaults to 6000ms.
52-
# Suggest a much longer time (5 minutes)
53-
zookeeper.connection.timeout.ms=300000
51+
# Timeout in ms for connecting to zookeeper defaults to 6000ms.
52+
# Suggest a much longer time (5 minutes)
53+
zookeeper.connection.timeout.ms=300000
5454

5555
By default, Kafka will automatically create topics.
5656
This means you could accidentally start an alarm server for a non-existing configuration.
@@ -60,11 +60,13 @@ Best disable auto-topic-creation, create topics on purpose with the correct sett
6060
and have alarm tools that try to access a non-existing configuration fail.
6161

6262
# Suggest to add this to prevent automatic topic creation,
63-
auto.create.topics.enable=false
63+
auto.create.topics.enable=false
6464

6565
If the following "First steps" generate errors of the type
6666

6767
WARN Error while fetching metadata with correlation id 39 : .. LEADER_NOT_AVAILABLE
68+
or
69+
ERROR ..TimeoutException: Timed out waiting for a node assignment
6870

6971
then define the host name in `config/server.properties`.
7072
For tests, you can use localhost:
@@ -111,13 +113,13 @@ It is not required for the alarm system setup
111113
but simply meant to learn about Kafka or to test connectivity.
112114

113115
# Create new topic
114-
kafka/bin/kafka-topics.sh --zookeeper localhost:2181 --create --replication-factor 1 --partitions 1 --topic test
116+
kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --create --replication-factor 1 --partitions 1 --topic test
115117

116118
# Topic info
117-
kafka/bin/kafka-topics.sh --zookeeper localhost:2181 --list
118-
kafka/bin/kafka-topics.sh --zookeeper localhost:2181 --describe
119-
kafka/bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic test
120-
kafka/bin/kafka-configs.sh --zookeeper localhost:2181 --entity-type topics --describe
119+
kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --list
120+
kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --describe
121+
kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --describe --topic test
122+
kafka/bin/kafka-configs.sh --bootstrap-server localhost:9092 --entity-type topics --describe
121123

122124
# Produce messages for topic (no key)
123125
kafka/bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
@@ -133,7 +135,7 @@ but simply meant to learn about Kafka or to test connectivity.
133135
kafka/bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --property print.key=true --property key.separator=": " --topic test --from-beginning
134136

135137
# Delete topic
136-
kafka/bin/kafka-topics.sh --zookeeper localhost:2181 --delete --topic test
138+
kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --delete --topic test
137139

138140

139141
Stop local instance:

0 commit comments

Comments
 (0)