[KAFKA-13398] The caller program will be shut down directly when the execution of Kafka script is abnormal

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.0.0
• Component/s: admin
• Assignee: Unassigned
• Reporter: RivenSun
• Reviewer: Guozhang Wang
• Created: 25/Oct/21 09:08
• Updated: 23/Apr/22 00:59
• Resolved: 23/Apr/22 00:59

Description

hello showuon and guozhang

Kafka has some key functions that have not yet been integrated into Java-AdminClient, so I have to use some Scala classes in the Kafka Server `kafka.admin` package in my java program, such as: `ReassignPartitionsCommand`, `ConsumerGroupCommand` (reset group offsets),  and etc., to call their `main(args: Array[String])` methods in order to achieve specific functions.

Problem:

1. In different Kafka versions, these Scala classes may have different requirements for input parameters, or they may have different treatments for the results of command execution.
1) `ReassignPartitionsCommand` requires  --bootstrap-server is required in the latest high version,

but requires --zookeeper in the low version.
Once the parameter verification fails, the Exit.exit(1, Some(message)) method will be called, which will cause my process to shut down directly.
2) In Kafka 3.0.0 version, there is this code at the end in the `main(args: Array[String])` method of `ReassignPartitionsCommand`

// If the command failed, exit with a non-zero exit code.
 if (failed) {
 Exit.exit(1)
 }

This will also make my process shut down directly

So I hope that the Kafka community will be able to print out the reason and stack of the corresponding exception when the parameter verification fails or the execution command is abnormal, and then return from the `main(args: Array[String])` method of the command, but don't call `Exit.exit(...)` method. Of course, when the script is executed on the machine, there is no problem with exiting directly.