Hi,
We've recently hit an issue that is marked as "resolved" in the 0.10
branch, but has never been released[1]. There is no known workaround for
the problem.
Upgrading our cluster to a 0.11 version is certainly an option, but is a
risky one given that it could introduce move bugs (especially sin
y the fix? Is this a known problem in
0.8.1.1?
Thanks,
Philippe
[1] https://issues.apache.org/jira/browse/KAFKA-612
On Wed, Feb 18, 2015 at 12:21 AM, Philippe Laflamme
wrote:
> Hi,
>
> I'm trying to replicate a broker shutdown in unit tests. I've got a simple
> cluster runn
Hi,
I'm trying to replicate a broker shutdown in unit tests. I've got a simple
cluster running with 2 brokers (and one ZK). I'm successfully able to
create a topic with a single partition and replication factor of 2.
I'd like to test shutting down the current leader for the partition and
make sur
Sorry for adding noise, but I think Jan has a very good point: applications
shouldn't be forced to create multiple producers simply to wire-in the
proper Serializer. It's an artificial restriction that wastes resources.
It's a common thing for us to create a single producer and slap different
"vie
; not get enough traffic to make it dirty the log cleaner will not kicks in
> to that partition again.
>
> Guozhang
>
>
> On Tue, Aug 26, 2014 at 9:02 AM, Philippe Laflamme
> wrote:
>
> > Here's the thread dump:
> > https://gist.github.com/plaflamme/634411b162f5
gt;
> Guozhang
>
> Gu
>
>
> On Tue, Aug 26, 2014 at 8:15 AM, Philippe Laflamme
> wrote:
>
> > Hi,
> >
> > We're using compaction on some of our topics. The log cleaner output
> showed
> > that it kicked in when the broker was restarted. Bu
Hi,
We're using compaction on some of our topics. The log cleaner output showed
that it kicked in when the broker was restarted. But now after several
months of uptime, the log cleaner output is empty. The compacted topics
segment files don't seem to be cleaned up (compacted) anymore.
If there an
