Cool. Would you mind describing the bug so it helps other Kafka users as
well?
On Sat, Mar 8, 2014 at 8:45 AM, Bae, Jae Hyeon wrote:
> Never mind, this was caused by a bug of my apache curator-zkclient bridge
> module.
>
>
> On Fri, Mar 7, 2014 at 6:14 PM, Bae, Jae Hyeon wrote:
>
> > I started
Never mind, this was caused by a bug of my apache curator-zkclient bridge
module.
On Fri, Mar 7, 2014 at 6:14 PM, Bae, Jae Hyeon wrote:
> I started from a fresh but I deployed the working version synced from the
> latest trunk, not a release version.
>
> I just executed kafka.admin.TopicCommand
I started from a fresh but I deployed the working version synced from the
latest trunk, not a release version.
I just executed kafka.admin.TopicCommand with --create option.
On Fri, Mar 7, 2014 at 5:56 PM, Neha Narkhede wrote:
> Starting from a fresh and working deployment, what admin command
Starting from a fresh and working deployment, what admin commands or steps
lead you to these errors? This error basically points to an unexpected
state change, which could be a bug. I'm looking for steps to be able to
reproduce the bug.
Thanks,
Neha
On Fri, Mar 7, 2014 at 1:59 PM, Bae, Jae Hyeon
How can I prevent these errors coming?
When I created 9 partitions on 3 instances and 2 replication-factor, I
didn't have any error. But when I created 36 partitions on 12 instances, I
got these errors.
2014-03-07 18:19:28,208] ERROR Controller 9 epoch 12 initiated state change
of replica 9 for
