[
https://issues.apache.org/jira/browse/KAFKA-9709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057519#comment-17057519
]
qiang Liu commented on KAFKA-9709:
----------------------------------
create a pull request [https://github.com/apache/kafka/pull/8275] which simply
add a confirm.
but as @rondagostino pointed out in that pull request, this change existing
behavior, so maybe we should done this in a better way.
thinking up some , list them below
# add a delay like 5 seconds, if no user interaction, do kill all just as
before, may add a arg like killall to skip the wait
# create another script name it like kafka-server-stop-single.sh which will
not do the kill when find multiple instance
> add a confirm when kafka-server-stop.sh find multiple kafka instances to kill
> -----------------------------------------------------------------------------
>
> Key: KAFKA-9709
> URL: https://issues.apache.org/jira/browse/KAFKA-9709
> Project: Kafka
> Issue Type: Improvement
> Components: admin
> Affects Versions: 2.4.1
> Reporter: qiang Liu
> Priority: Minor
>
> currently kafka-server-stop.sh find all kafka instances on the machine and
> kill them all with out any confirm, when deploy multity instance in one
> machine, some may mistakenly kill all instance while only mean to kill single
> one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
