Coming back to this issue, looks like it was a result of the centos 7
systemd cleanup task on tmp:
/usr/lib/tmpfiles.d/tmp.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License
servers have not been restarted any time lately. The uptime for all the 3
> servers is almost 67 days.
>
> Regards,
> Rahul Misra
>
>
> -Original Message-
> From: Madhukar Bharti [mailto:bhartimadhu...@gmail.com]
> Sent: Wednesday, June 22, 2016 8:37 PM
> To: user
@gmail.com]
Sent: Wednesday, June 22, 2016 8:37 PM
To: users@kafka.apache.org
Subject: Re: Kafka broker crash
Hi Rahul,
Whether the path is "/tmp/kafka-logs/" or "/temp/kafka-logs" ?
Mostly if path is set to "/tmp/" then in case machine restart it
Hi Rahul,
Whether the path is "/tmp/kafka-logs/" or "/temp/kafka-logs" ?
Mostly if path is set to "/tmp/" then in case machine restart it may delete
the files. So it is throwing FileNotFoundException.
you can change the file location to some other path and restart all broker.
This might fix the
Hi Ben,
Thanks for responding. I can't imagine what would have cleaned temp up at
that time. I don't think we have anything in place to do that, it also
appears to happened to both machines at the same time.
It also appears that the other topics were not affected, there were still
other files pre
Possibly tmp got cleaned up?
Seems like one of the log files where deleted while a producer was writing
messages to it:
On Thursday, 26 May 2016, cs user wrote:
> Hi All,
>
> We are running Kafka version 0.9.0.1, at the time the brokers crashed
> yesterday we were running in a 2 mode cluster. T
