Help with kafka broker reporting offset out of range after unclean shutdown

2023-10-09 Thread Steve Jacobs (US)
I opened this issue 3 weeks ago on the issue tracker: https://issues.apache.org/jira/browse/KAFKA-15467 Every time I lose power at one of these remote hosts, when the power comes back up and the broker restarts, I have several (not all) topics report offsets as missing back to mirrormaker2, resu

Re: What is causing Broker Unclean shutdown

2016-11-16 Thread Guozhang Wang
[Kafka Server 1], Retrying > > controlled shutdown after the previous attempt failed... > > WARN kafka.server.KafkaServer - [Kafka Server 1], Proceeding to do > > an unclean shutdown as all the controlled shutdown attempts failed > > INFO kafka.network.SocketServer - [Socket

Re: What is causing Broker Unclean shutdown

2016-11-14 Thread Zakee
Retrying > controlled shutdown after the previous attempt failed... > WARN kafka.server.KafkaServer - [Kafka Server 1], Proceeding to do > an unclean shutdown as all the controlled shutdown attempts failed > INFO kafka.network.SocketServer - [Socket Server on Broker 1], Shutting down &

What is causing Broker Unclean shutdown

2016-11-12 Thread Vinay Gulani
Hi, I am getting below warning message: WARN kafka.server.KafkaServer - [Kafka Server 1], Retrying controlled shutdown after the previous attempt failed... WARN kafka.server.KafkaServer - [Kafka Server 1], Proceeding to do an unclean shutdown as all the controlled shutdown attempts failed

Recovery skipped after unclean shutdown

2015-09-02 Thread Pradeep Jawahar
One of the brokers in our cluster had an unclean shutdown and after it was restated I found the following logs. $ grep "clean shutdown" /var/groupon/kafka/kafka-broker.log 02/Sep/2015 16:19:23 - warn::[Kafka Server 1], Proceeding to do an unclean shutdown as all the controlled shutdow

Re: expected behavior if a node undergoes unclean shutdown

2015-04-08 Thread Jason Rosenberg
the bottom of an issue we had previously, with > an unclean shutdown during an upgrade to 0.8.2.1 (from 0.8.1.1). In that > case, the controlled shutdown was interrupted, and the node was shutdown > abruptly. This resulted in about 5 minutes of unavailability for most > partitions.

expected behavior if a node undergoes unclean shutdown

2015-04-08 Thread Jason Rosenberg
Hello, I'm still trying to get to the bottom of an issue we had previously, with an unclean shutdown during an upgrade to 0.8.2.1 (from 0.8.1.1). In that case, the controlled shutdown was interrupted, and the node was shutdown abruptly. This resulted in about 5 minutes of unavailabilit

Re: unclean shutdown

2013-10-14 Thread Kane Kane
y expectation would be that broker will try to restore or delete it > > itself. > > > > > > On Mon, Oct 14, 2013 at 5:55 PM, Sriram Subramanian < > > srsubraman...@linkedin.com> wrote: > > > > > Is this a bug? Can an unclean shutdown leave the ind

Re: unclean shutdown

2013-10-14 Thread Jun Rao
ote: > > > Is this a bug? Can an unclean shutdown leave the index in a corrupt state > > that the broker cannot start (expected state)? > > > > On 10/14/13 4:52 PM, "Neha Narkhede" wrote: > > > > > It is possible that the unclean broker shutdow

Re: unclean shutdown

2013-10-14 Thread Kane Kane
Yes, my expectation would be that broker will try to restore or delete it itself. On Mon, Oct 14, 2013 at 5:55 PM, Sriram Subramanian < srsubraman...@linkedin.com> wrote: > Is this a bug? Can an unclean shutdown leave the index in a corrupt state > that the broker cannot start (ex

Re: unclean shutdown

2013-10-14 Thread Sriram Subramanian
Is this a bug? Can an unclean shutdown leave the index in a corrupt state that the broker cannot start (expected state)? On 10/14/13 4:52 PM, "Neha Narkhede" wrote: > It is possible that the unclean broker shutdown left the index in an >inconsistent state. You can delete the

Re: unclean shutdown

2013-10-14 Thread Kane Kane
x files, that will > > > make the Kafka server rebuild the index on startup. > > > > > > Thanks, > > > Neha > > > > > > > > > On Mon, Oct 14, 2013 at 3:05 PM, Kane Kane > > wrote: > > > > > > > After un

Re: unclean shutdown

2013-10-14 Thread Neha Narkhede
gt; > > > > On Mon, Oct 14, 2013 at 3:05 PM, Kane Kane > wrote: > > > > > After unclean shutdown kafka reports this error on startup: > > > [2013-10-14 16:44:24,898] FATAL Fatal error during KafkaServerStable > > > startup. Prepare to shutdown (kafka.server.Kafka

Re: unclean shutdown

2013-10-14 Thread Kane Kane
index files, that will > make the Kafka server rebuild the index on startup. > > Thanks, > Neha > > > On Mon, Oct 14, 2013 at 3:05 PM, Kane Kane wrote: > > > After unclean shutdown kafka reports this error on startup: > > [2013-10-14 16:44:24,898] FATAL Fatal

Re: unclean shutdown

2013-10-14 Thread Neha Narkhede
It is possible that the unclean broker shutdown left the index in an inconsistent state. You can delete the corrupted index files, that will make the Kafka server rebuild the index on startup. Thanks, Neha On Mon, Oct 14, 2013 at 3:05 PM, Kane Kane wrote: > After unclean shutdown ka

unclean shutdown

2013-10-14 Thread Kane Kane
After unclean shutdown kafka reports this error on startup: [2013-10-14 16:44:24,898] FATAL Fatal error during KafkaServerStable startup. Prepare to shutdown (kafka.server.KafkaServerStartable) java.lang.IllegalArgumentException: requirement failed: Corrupt index found, index file (/disk1/kafka