I think that is the default signal. >From the script: SIGNAL=${SIGNAL:-TERM}
FYI On Wed, Jan 10, 2018 at 2:35 AM, Sam Pegler <sam.peg...@infectiousmedia.com> wrote: > Have you tried a normal kill (sigterm) against the java process? > > __ > > Sam Pegler > > PRODUCTION ENGINEER > > T. +44(0) 07 562 867 486 > > <http://www.infectiousmedia.com/> > 3-7 Herbal Hill / London / EC1R 5EJ > www.infectiousmedia.com > > This email and any attachments are confidential and may also be privileged. > If you > are not the intended recipient, please notify the sender immediately, and > do not > disclose the contents to another person, use it for any purpose, or store, > or copy > the information in any medium. Please also destroy and delete the message > from > your computer. > > > On 9 January 2018 at 22:44, Skip Montanaro <skip.montan...@gmail.com> > wrote: > > > I only discovered the kafka-server-stop.sh script a couple days ago. I > > can't seem to make it do its thing (the corresponding zookeeper stop > > script seems to work just fine). All consumers have been stopped. Lsof > > still shows the Kafka broker process listening on its port. The last > > connection left the CLOSE_WAIT state several minutes ago. Gstack shows > > 169 threads, most in pthread_cond_wait(), a handful in other wait-like > > functions (sem_wait, pthread_join, pthread_cond_timedwait, poll, > > epoll_wait). I'm running 2.11-1.0.0 on a Red Hat 6 server. > > > > What does it take to get a broker to exit (short of kill -9)? > > > > Thx, > > > > Skip Montanaro > > >