Re: Partition reassignment reversed

2014-12-08 Thread Jun Rao
Topic deletion doesn't quite work in 0.8.1.1. It's fixed in the upcoming 0.8.2 release. Thanks, Jun On Wed, Dec 3, 2014 at 6:17 PM, Andrew Jorgensen < ajorgen...@twitter.com.invalid> wrote: > We are currently running 0.8.1.1, I just double checked. One other thing > that may be related is I bro

Re: Partition reassignment reversed

2014-12-04 Thread Andrew Jorgensen
We are currently running 0.8.1.1, I just double checked. One other thing that may be related is I brought up a second kafka cluster today matching the first. I noticed that if I deleted a topic and the re-created it with the same name when I re-created the topic none of the leader elections happ

Re: Partition reassignment reversed

2014-12-04 Thread Jun Rao
Not sure exactly what happened there. We did fix a few bugs in reassigning partitions in 0.8.1.1. So, you probably want to upgrade to that one or the upcoming 0.8.2 release. Thanks, Jun On Tue, Dec 2, 2014 at 2:33 PM, Andrew Jorgensen wrote: > I am using kafka 0.8. > Yes I did run —verify, but

Re: Partition reassignment reversed

2014-12-02 Thread Andrew Jorgensen
I am using kafka 0.8. Yes I did run —verify, but got some weird output from it I had never seen before that looked something like: Status of partition reassignment: ERROR: Assigned replicas (5,2) don't match the list of replicas for reassignment (5) for partition [topic-1,248] ERROR: Assigned re

Re: Partition reassignment reversed

2014-12-02 Thread Jun Rao
Did you run the --verify option ( http://kafka.apache.org/documentation.html#basic_ops_restarting) to check if the reassignment process completes? Also, what version of Kafka are you using? Thanks, Jun On Mon, Dec 1, 2014 at 7:16 PM, Andrew Jorgensen < ajorgen...@twitter.com.invalid> wrote: > I

Partition reassignment reversed

2014-12-01 Thread Andrew Jorgensen
I unfortunately do not have any specific logs from these events but I will try and describe the events as accurately as possible to give an idea of the problem I saw. The odd behavior manifested itself when I bounced all of the kafka processes on each of the servers in a 12 node cluster. A few