Thank you for testing and voting the release!
I noticed that the date for 1.1.1-rc1 is wrong. Please kindly test and vote
by Tuesday, June 26, 12 pm PT.
Thanks,
Dong
On Fri, Jun 22, 2018 at 10:09 AM, Dong Lin wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the second
+1 .
1. Ran unit tests.
2. Ran few tests on 3-node cluster
Thanks,
Harsha
On Fri, Jun 22nd, 2018 at 2:41 PM Jakob Homan wrote:
>
>
>
> +1 (binding)
>
> * verified sigs, NOTICE, LICENSE
> * ran unit tests
> * spot checked headers
>
> -Jakob
>
>
>
> On 22 June 2018 at 13:19, Ted Yu < y
Hello Kafka users, developers and client-developers,
This is the second candidate for release of Apache Kafka 0.10.2.2.
Note, that RC0 was created before the upgrade to Gradle 4.8.1 and thus,
we discarded it in favor of RC1 (without sending out a email for RC0).
This is a bug fix release closing
Hello Sam,
We have just back ported this fix into the 1.1 and 1.0 branch now:
https://github.com/apache/kafka/pull/5277
The up coming 1.1.1 and 1.0.2 release should have this issue fixed.
Guozhang
On Thu, Jun 21, 2018 at 2:36 PM, Sam Lendle wrote:
> Yep that’s the change I saw. It does look
+1 (non-binding)
Built from source and ran quickstart successfully on Ubuntu (with Java 8).
Thanks Matthias!
--Vahid
From: "Matthias J. Sax"
To: d...@kafka.apache.org, users@kafka.apache.org,
kafka-clie...@googlegroups.com
Date: 06/22/2018 03:14 PM
Subject:[VOTE] 0.11.0.3 RC
+1 (non-binding)
Built from source and ran quickstart successfully on Ubuntu (with Java 8
and Java 9).
Thanks Rajini!
--Vahid
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 0.11.0.3.
This is a bug fix release closing 27 tickets:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.3
Release notes for the 0.11.0.3 release:
http://home.apache.
+1 (binding)
* verified sigs, NOTICE, LICENSE
* ran unit tests
* spot checked headers
-Jakob
On 22 June 2018 at 13:19, Ted Yu wrote:
> +1
>
> Ran test suite.
> Checked signatures.
>
> On Fri, Jun 22, 2018 at 12:14 PM, Vahid S Hashemian <
> vahidhashem...@us.ibm.com> wrote:
>
>> +1 (non-binding)
+1
Ran test suite.
Checked signatures.
On Fri, Jun 22, 2018 at 12:14 PM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:
> +1 (non-binding)
>
> Built from source and ran quickstart successfully on Ubuntu (with Java 8).
>
> Thanks Dong!
> --Vahid
>
>
>
> From: Dong Lin
> To: d...@kaf
+1 (non-binding)
Built from source and ran quickstart successfully on Ubuntu (with Java 8).
Thanks Dong!
--Vahid
From: Dong Lin
To: d...@kafka.apache.org, users@kafka.apache.org,
kafka-clie...@googlegroups.com
Date: 06/22/2018 10:10 AM
Subject:[VOTE] 1.1.1 RC1
Hello Kafka
I am using a session store in a kafka streams application. With caching turned
on, average fetch latency was very high, about 200 ms after running for about 1
hour. With caching turned off, it was about 100 μs. We seem to be running fine
without caching, but I am very curious as to why caching p
Martin,
I think I tried that already. I setup a user in ad and assigned the shared
SPN record for the ELB to that user. I then added the user to the keytab
file for the kafka servers and had the kafka servers use the SPN for the
user with the dns record. That worked fine for authing through the EL
+1 (non-binding)
Built from source and ran quickstart successfully on Ubuntu (with Java 8).
Thanks for running the release Matthias!
--Vahid
From: "Matthias J. Sax"
To: d...@kafka.apache.org, users@kafka.apache.org,
kafka-clie...@googlegroups.com
Date: 06/22/2018 10:42 AM
Subject:
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 1.0.2.
This is a bug fix release closing 26 tickets:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+1.0.2
Release notes for the 1.0.2 release:
http://home.apache.org/~mjsa
it appears you want:
common-principal name with common-key distributed to all subdomains
Use only one common Service Principal Name:
One of the solutions is to create a new Service Principal in the KDC for
the name HTTP/all.ipa@ipa.dom
then generate a keytab and
distribute it (keytab) to a
Hi John,
I think the situation you describe is reasonable but we can still do some
tricks there. For example, filter out the aggregated metrics with the
aggregated "count" (sum of total number of metrics in the aggregation) less
than some threshold. So to make things simpler, we can assume that th
Hello Kafka users, developers and client-developers,
This is the second candidate for release of Apache Kafka 1.1.1.
Apache Kafka 1.1.1 is a bug-fix release for the 1.1 branch that was first
released with 1.1.0 about 3 months ago. We have fixed about 25 issues since
that release. A few of the mor
Ben,
Yes. I want to be able to provide consumers/producers with a single address
they can use to connect to the cluster. Having it behind an elb lets us
scale up and replace nodes with out needing to mess with consumer/producer
configurations. I have considered setting up individual dns records fo
Hey Tyler,
What is your end goal? To have a single publicly / internally available
address to be able to provide to consumers / producers to connect to the
Kerberized Kafka?
On Fri, Jun 22, 2018 at 9:20 AM, Tyler Monahan wrote:
> Martin,
>
> I have read that stack overflow post but it doesn't h
Martin,
I have read that stack overflow post but it doesn't help with my specific
problem. An ELB will work if I am not using kerberos just fine. The issue
started happening when I added kerberos auth to the cluster. The auth has
to happen before the meta data request so it never gets to the point
Any and all testing is welcome, but testing in the following areas would be
particularly helpful:
1. Performance and stress testing. Heroku and LinkedIn have helped with this
in the past (and issues have been found and fixed).
2. Client developers can verify that their clients can produce
MG>quoting stackoverflow below
"You can use an ELB as the bootstrap.servers,
The ELB will be used for the initial metadata request the client makes to
figure out which topic partitions are on which brokers,
but after (the initial metadata request)
the brokers still need to be directly accessible
22 matches
Mail list logo
