In trunk, we have a JMX monitoring the states of each broker. One of the
states is log recovery.

Thanks,

Jun


On Mon, May 19, 2014 at 11:15 AM, Jonas Bergström <luckysw...@gmail.com>wrote:

> Ok, I'll upgrade.
> Is there a way to see the status of a node that is recovering, e.g. in
> zookeeper or via jmx?
>
> / Jonas
>
>
> 2014-05-19 16:49 GMT+02:00 Jun Rao <jun...@gmail.com>:
>
> > Do you think you could upgrade to 0.8.1.1? It fixed a bunch of corner
> cases
> > in the controller.
> >
> > Thanks,
> >
> > Jun
> >
> >
> > On Mon, May 19, 2014 at 12:00 AM, Jonas Bergström <luckysw...@gmail.com
> > >wrote:
> >
> > > I'm running Kafka 0.8.
> > >
> > > / Jonas
> > >
> > >
> > > 2014-05-18 23:45 GMT+02:00 Jonas Bergström <luckysw...@gmail.com>:
> > >
> > > > Hi all, and thanks for a fantastic product.
> > > >
> > > > The other day our kafka node in our test environment went down due to
> > > full
> > > > disc. I reconfigured kafka to save fewer messages, and restarted the
> > > node.
> > > > It is a single node setup. At restart the node freed up some disc
> > space,
> > > > but no new messages where accepted. In the log we saw this:
> > > >
> > > > WARN [KafkaApi-0] Produce request with correlation id 12680557 from
> > > > client  on partition [logs,0] failed due to Partition [logs,0]
> doesn't
> > > > exist on 0 (kafka.server.KafkaApis)
> > > >
> > > > List-topics showed:
> > > >
> > > > topic: logs partition: 0 leader: 0 replicas: 0 isr: 0
> > > >
> > > > which seemed fine, but I figured I might have to reassign the topic
> > > > partition anyway, so I did. Nothing seemed to happen, neither in the
> > logs
> > > > or in the status. Then I got another thing to take care of for
> awhile,
> > > and
> > > > realized about 30 minutes later that the node started working again!
> > > >
> > > > Is this expected behavior? How long does a node take to "get online"
> > > again
> > > > after a crash-restart? Is there a way to tell that the node is on
> it's
> > > way
> > > > up?
> > > >
> > > >
> > > > Thanks / Jonas
> > > >
> > >
> >
>

Reply via email to