Kafka and ZooKeeper Configuration Issues: Cluster ID, Topic Deletion

Hello Kafka Community,

I’m currently facing a set of challenges with my Kafka and ZooKeeper setup on an Azure Ubuntu VM. I would greatly appreciate your insights and guidance on the following issues:

1. ZooKeeper Cluster ID and DataDir: After each VM restart, ZooKeeper generates a new cluster ID, causing synchronization problems with Kafka. I understand that changing the dataDir to a persistent location can resolve this. I have updated it to /var/zookeeper , but I’m open to suggestions and best practices.

Zookeeper Configuration

Systemctl status Zookeeper:

**root@CNAS-STACKSTORM-DEV-1:/home/azureuser# systemctl status zookeeper**
**● zookeeper.service**
**     Loaded: loaded (/etc/systemd/system/zookeeper.service; enabled; vendor preset: enabled)**
**     Active: failed (Result: exit-code) since Mon 2023-11-20 06:55:51 UTC; 5s ago**
**    Process: 99111 ExecStart=/home/kafka/kafka/bin/zookeeper-server-start.sh /home/kafka/kafka/config/zookeeper.properties (code=exited, status=3)**
**   Main PID: 99111 (code=exited, status=3)**

**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]:         at org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperSe>**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]:         at org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeepe>**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]:         at org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.>**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]:         at org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(Quorum>**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]:         at org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.jav>**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]: Unable to access datadir, exiting abnormally**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]: [2023-11-20 06:55:51,657] INFO ZooKeeper audit is disabled. (org.apache.zookeeper.au>**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 zookeeper-server-start.sh[99111]: [2023-11-20 06:55:51,658] ERROR Exiting JVM with code 3 (org.apache.zookeeper.util.S>**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 systemd[1]: zookeeper.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED**
**Nov 20 06:55:51 CNAS-STACKSTORM-DEV-1 systemd[1]: zookeeper.service: Failed with result 'exit-code'.**

2. Kafka Topic Deletion: I’ve observed that all of my Kafka topics are getting deleted. I want to ensure that topics persist across restarts. Is there a specific Kafka broker configuration I should review? The delete.topic.enable property in server.properties is currently set to false

3. Kafka Producer Error: When attempting to publish messages using the Kafka console producer, I encounter the following error:

ERROR Error when sending message to topic XXX with key: null, value: X bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)

I’ve verified my producer and broker configurations, but the issue persists. Any insights or suggestions on troubleshooting this would be immensely helpful.

Thank you in advance for your assistance!

Hi everyone,

I posted a question , but I haven’t received any responses yet. I would really appreciate any insights or guidance you can provide. Thanks in advance!

Configuration details:
Kafka Version: 3.5.0

Server.Properties Config file:

############################# Server Basics #############################

# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0

############################# Socket Server Settings #############################

# The address the socket server listens on. If not configured, the host name will be equal to the value of
# java.net.InetAddress.getCanonicalHostName(), with PLAINTEXT listener name, and port 9092.
#   FORMAT:
#     listeners = listener_name://host_name:port
#   EXAMPLE:
#     listeners = PLAINTEXT://your.host.name:9092
#listeners=PLAINTEXT://:9092
listeners=PLAINTEXT://X.X.X.X:9092



# Listener name, hostname and port the broker will advertise to clients.
# If not set, it uses the value for "listeners".
advertised.listeners=PLAINTEXT://X.X.X.X:9092


# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL

# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3

# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8

# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400

# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400

# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600

############################# Log Basics #############################

# A comma separated list of directories under which to store log files
log.dirs=/home/kafka/logs

# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1

# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1

############################# Internal Topic Settings  #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1

############################# Log Flush Policy #############################

# Messages are immediately written to the filesystem but by default we only fsync() to sync
# the OS cache lazily. The following configurations control the flush of data to disk.
# There are a few important trade-offs here:
#    1. Durability: Unflushed data may be lost if you are not using replication.
#    2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
#    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
# The settings below allow one to configure the flush policy to flush data after a period of time or
# every N messages (or both). This can be done globally and overridden on a per-topic basis.

# The number of messages to accept before forcing a flush of data to disk
#log.flush.interval.messages=10000

# The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms=1000

############################# Log Retention Policy #############################

# The following configurations control the disposal of log segments. The policy can
# be set to delete segments after a period of time, or after a given size has accumulated.
# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens 
# from the end of the log.

# The minimum age of a log file to be eligible for deletion due to age
log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824

# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824

# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000

############################# Zookeeper #############################

# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=18000

############################# Group Coordinator Settings #############################

# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=0


auto.leader.rebalance.enable=true

#log.cleaner.enable=true

producer.properties config file

############################# Producer Basics #############################

# list of brokers used for bootstrapping knowledge about the rest of the cluster
# format: host1:port1,host2:port2 ...
bootstrap.servers=X.X.X.X:9092

# specify the compression codec for all data generated: none, gzip, snappy, lz4, zstd
compression.type=none

# name of the partitioner class for partitioning records;
# The default uses "sticky" partitioning logic which spreads the load evenly between partitions, but improves throughput by attempting to fill the batches sent to each partition.
#partitioner.class=

# the maximum amount of time the client will wait for the response of a request
#request.timeout.ms=

# how long `KafkaProducer.send` and `KafkaProducer.partitionsFor` will block for
#max.block.ms=

# the producer will wait for up to the given delay to allow other records to be sent so that the sends can be batched together
#linger.ms=

# the maximum size of a request in bytes
#max.request.size=

# the default batch size in bytes when batching multiple records sent to a partition
#batch.size=

# the total bytes of memory the producer can use to buffer records waiting to be sent to the server
#buffer.memory=

consumer.properties config file

#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# see org.apache.kafka.clients.consumer.ConsumerConfig for more details

# list of brokers used for bootstrapping knowledge about the rest of the cluster
# format: host1:port1,host2:port2 ...
#bootstrap.servers=localhost:9092
bootstrap.servers=X.X.X.X:9092


# consumer group id
group.id=test-group

# What to do when there is no initial offset in Kafka or if the current
# offset does not exist any more on the server: latest, earliest, none
#auto.offset.reset=earliest



# Zookeeper connection string
# comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002"
#zookeeper.connect=127.0.0.1:2181
#zookeeper.connect=X.X.X.X:2181

# timeout in ms for connecting to zookeeper
#zookeeper.connection.timeout.ms=6000

zookeeper.properties

#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# the directory where the snapshot is stored.
dataDir=/var/zookeeper
# the port at which the clients will connect
clientPort=2181
# disable the per-ip limit on the number of connections since this is a non-production config
maxClientCnxns=0
# Disable the adminserver by default to avoid port conflicts.
# Set the port to something non-conflicting if choosing to enable this
admin.enableServer=false
# admin.serverPort=8080