Сервер Apache Kafka Автоматически останавливается через некоторое время

#apache-kafka

Вопрос:

Я использую apache Kafka для одного из проектов. Сервер Kafka автоматически останавливается после того, как я запустил его в течение 1 дня. Может ли кто-нибудь сказать мне, какое свойство конфигурации мне нужно изменить? Он работает после удаления файлов журнала в течение некоторого времени, и одна и та же проблема повторяется непрерывно. может ли кто-нибудь, пожалуйста, предложить решение для этого?

Сервер Кафки.свойства

 # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # 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 kafka.server.KafkaConfig for additional details and defaults  ############################# 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. It will get the value returned from  # java.net.InetAddress.getCanonicalHostName() if not configured. # FORMAT: # listeners = listener_name://host_name:port # EXAMPLE: # listeners = PLAINTEXT://your.host.name:9092 listeners=PLAINTEXT://:9092  # Hostname and port the broker will advertise to producers and consumers. If not set,  # it uses the value for "listeners" if configured. Otherwise, it will use the value # returned from java.net.InetAddress.getCanonicalHostName(). #advertised.listeners=PLAINTEXT://your.host.name:9092 advertised.listeners=PLAINTEXT://*.*.*.*: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=/centos/home/kafka/tmp/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  

и смотритель зоопарка.свойства

 # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at #  # 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=/tmp/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  

И файл журнала сервера содержит сообщение ниже

 [2021-11-16 06:25:07,521] WARN Unexpected exception (org.apache.zookeeper.server.NIOServerCnxn) EndOfStreamException: Unable to read additional data from client, it probably closed the socket: address = /0:0:0:0:0:0:0:1:52984, session = 0x1005ceb08740001  at org.apache.zookeeper.server.NIOServerCnxn.handleFailedRead(NIOServerCnxn.java:163)  at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:326)  at org.apache.zookeeper.server.NIOServerCnxnFactory$IOWorkRequest.doWork(NIOServerCnxnFactory.java:522)  at org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:154)  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)  at java.lang.Thread.run(Thread.java:748) [2021-11-16 06:25:07,537] INFO Expiring session 0x1005ceb08740001, timeout of 18000ms exceeded (org.apache.zookeeper.server.ZooKeeperServer) [2021-11-16 06:25:58,618] INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$) [2021-11-16 06:25:59,324] INFO Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation (org.apache.zookeeper.common.X509Util) [2021-11-16 06:25:59,488] INFO Registered signal handlers for TERM, INT, HUP (org.apache.kafka.common.utils.LoggingSignalHandler) [2021-11-16 06:25:59,492] INFO starting (kafka.server.KafkaServer) [2021-11-16 06:25:59,499] INFO Connecting to zookeeper on localhost:2181 (kafka.server.KafkaServer) [2021-11-16 06:25:59,520] INFO [ZooKeeperClient Kafka server] Initializing a new session to localhost:2181. (kafka.zookeeper.ZooKeeperClient) [2021-11-16 06:25:59,533] INFO Client environment:zookeeper.version=3.6.3--6401e4ad2087061bc6b9f80dec2d69f2e3c8660a, built on 04/08/2021 16:35 GMT (org.apache.zookeeper.ZooKeeper) [2021-11-16 06:25:59,533] INFO Client environment:host.name=ip-172-31-32-15.ap-south-1.compute.internal (org.apache.zookeeper.ZooKeeper) [2021-11-16 06:25:59,533] INFO Client environment:java.version=1.8.0_302 (org.apache.zookeeper.ZooKeeper) [2021-11-16 06:25:59,533] INFO Client environment:java.vendor=Red Hat, Inc. (org.apache.zookeeper.ZooKeeper) [2021-11-16 06:25:59,533] INFO Client environment:java.home=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.302.b08-0.el8_4.x86_64/jre (org.apache.zookeeper.ZooKeeper)  

Комментарии:

1. Когда он останавливается, какая причина отображается в журнале сервера Kafka?

2. Я отредактировал свой вопрос с сообщением об ошибке, пожалуйста, проверьте

3. После этого в файле журнала нет другого содержимого? Похоже, что сервер работает с этого INFO starting (kafka.server.KafkaServer)