Hi Dong,
Is there a RC1 planned with configs documentation fixes and
https://github.com/apache/kafka/pull/5857 ?
Thanks,
Satish.
On Thu, Nov 1, 2018 at 4:05 PM Jakub Scholz wrote:
>
> +1 (non-binding) ... I used the staged binaries and checked it with
> different clients.
>
> On Wed, Oct 24, 2018
Recently,I had some problems when using kafka consumer AIPs.(The broker and
replicas number are 3) There is the error log:
10:42:40:446 INFO [FetchSessionHandler] [Consumer clientId=mbGW4rH5,
groupId=group-mbGW4rH5] Node 2 sent an invalid full fetch response
with extra=(mbGW4rH5-0, response=(
10:4
Hi, Mani,
Thanks for running the release. Verified quickstart on 2.12 binary. +1
Jun
On Thu, Oct 25, 2018 at 7:28 PM, Manikumar
wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the first candidate for release of Apache Kafka 2.0.1.
>
> This is a bug fix release closing
Hi
In Kafka topic data is split into partitions. Partitions are assigned to
brokers.
I assume what you are trying to says is that the distribution of messages
across partitions is not balanced.
Messages are written to topics as key,value. The messages are distributed
across partitions based on k
Hi Kafka experts,
We have a 3 nodes kafka setup with data streams from mysql binlog, we
noticed that from grafana monitoring in and out, some broker nodes are
having lower data ingested in and out, is there anyway to balance it? Or it
is nature of Kafka?
Thanks!
+1 (non-binding)
- Checked signatures
- Ran through quickstart on kafka_2.12-2.0.1.tgz
- Built from source with Java 8
On Mon, Nov 5, 2018 at 9:13 AM Satish Duggana wrote:
>
> +1 (non-binding)
>
> - Ran testAll/releaseTarGzAll on 2.0.1
> - Ran through quickstart of core/streams on builds generated
+1 (non-binding)
- Ran testAll/releaseTarGzAll on 2.0.1
- Ran through quickstart of core/streams on builds generated from tag
- Ran few internal apps targeting to topics on 3 node cluster.
Thanks,
Satish.
On Sat, Nov 3, 2018 at 2:32 AM Ewen Cheslack-Postava wrote:
>
> +1
>
> -Ewen
>
> On Thu, No