Hi,
With Kafka 0.8.1.1, I'm continuously running into the issue with no disk
space remaining. I'm observing that on the problematic brokers partitions
are distributed across several identical disks very unevenly. For example,
provided the fact that partitions have similar size, I see 6 partitions
I also noticed that some disks do not contain any partitions which is even
more strange. Why does broker not use them, while other disks are
overloaded?
2014-12-25 12:07 GMT+03:00 Yury Ruchin :
> Hi,
>
> With Kafka 0.8.1.1, I'm continuously running into the issue with no disk
> space remaining. I
Hi,
LogManager.nextLogDir() has the logic for choosing which directory to use.
The documentation of the method says:
/**
* Choose the next directory in which to create a log. Currently this is
done
* by calculating the number of partitions in each directory and then
choosing the
* data
IMO:
KAFKA-1790 - can be pushed out (or even marked as "won't fix")
KAFKA-1782 - can be pushed out (not really a blocker)
The rest look like actual blockers to me.
Gwen
On Tue, Dec 23, 2014 at 1:32 PM, Otis Gospodnetic <
otis.gospodne...@gmail.com> wrote:
> Hi,
>
> I see 16 open issues for 0.8.
Hi all,
I have a question about kafka,
Kafka producer speed is different from internet. And the capacity is
different with different versions.
I test this through kafka-producer-perf-test.sh.
1. Could you let me know the general send speed through thread: 1
batch:1, and the cor