Use the command kafka-server-stop.sh to close the Kafka service. If it is found that it cannot be deleted, an error is reported, as shown in the following figure
Modify Kafka server stop.sh
to
PIDS=$(ps ax | grep -i 'kafka\.Kafka' | grep java | grep -v grep | awk '{print $1}')
Change to
PIDS=$(jps -lm | grep -i 'kafka.Kafka'| awk '{print $1}')
command details: use the JPS – LM command to list all Java processes, then screen out the Kafka process through the pipeline by using the grep – I ‘Kafka. Kafka’ command, and finally take out the process number by using awk
The specific modification is shown in the figure below
test:
ok!
Similar Posts:
- Kafka official kafka-server-start.sh cannot close Kafka process solution
- Kafka startup error & problem solving
- [Solved] Kafka memory overflow: FATAL Fatal error during KafkaServerStartable startup. Prepare to shutdown
- [Solved] kafka Startup Error: Error: VM option ‘UseG1GC’ is experimental and must be enabled via -XX:+UnlockExperimentalVMOptions.
- Kafka Error: Error while executing topic command : Replication factor: 3 larger than available brokers: 0.
- [Solved] ClassNotFoundException: org.apache.storm.kafka.spout.KafkaSpoutConfig
- Kafka creates topic error: org.apache.kafka.common.errors.InvalidReplicationFactorException: Replication factor: 1 larger than available brokers: 0.
- Kafka Start Error: Corrupt index found & org.apache.kafka.common.protocol.types.SchemaException: Error reading field ‘version’: java.nio.BufferUnderflowException
- kafka java.net.ConnectException: Connection timed out: no further information
- kafka java.net.ConnectException: Connection timed out: no further information