Hello,
We are currently using kafka1.1.1 and planning to upgrade to kafka2.0,
I noticed all of them are using guava-20.0.jar which has a security
vulnerability right now. Could you update the guava version to 24.1.1
or higher to fix it, please? Link to the guava vulnerability:
https://github.com/go
Hello,
I have downloaded the source code for tag *2.1.1-rc1* (667980043). Executed
integration and unit tests:
*BUILD SUCCESSFUL in 25m 34s*
*136 actionable tasks: 133 executed, 3 up-to-date*
Also, I have downloaded the artifact from
http://home.apache.org/~cmccabe/kafka-2.1.1-rc1/kafka_2.11-2.
I couldn't repro locally, that was on an m3.large. And it's not happening
anymore. Might be a transient issue.
Thanks,
Eno
On Wed, Jan 30, 2019 at 6:46 PM Colin McCabe wrote:
> (+all lists)
>
> Hi Eno,
>
> Thanks for testing this.
>
> Those tests passed in the Jenkins build we did here:
> https
Tests of 3.4 branch are passing on jdk11.
Personally I have only experience of 3.5 in production with jdk11.
Enrico
Il giorno mer 30 gen 2019, 20:12 Mark Anderson ha
scritto:
> Hi all,
>
> Since Kafka 2.1 supports Java 11 we are considering moving to take
> advantage of performance improvement
Hi all,
Since Kafka 2.1 supports Java 11 we are considering moving to take
advantage of performance improvements since Java 8.
One issue that isn't clear to me is whether the latest Zookeeper 3.4.x
release supports Java 11.
Does anyone know? And if so are there any issues to watch out for?
Than
(+all lists)
Hi Eno,
Thanks for testing this.
Those tests passed in the Jenkins build we did here:
https://builds.apache.org/job/kafka-2.1-jdk8/118/
Perhaps there is an environment issue at play here? Do you get the same
failures running those tests on the 2.1 release?
Best,
Colin
On Wed, Ja
Hi Eno,
Thanks for testing this.
Those tests passed in the Jenkins build we did here:
https://builds.apache.org/job/kafka-2.1-jdk8/118/
Perhaps there is an environment issue at play here? Do you get the same
failures running those tests on the 2.1 release?
Best,
Colin
On Wed, Jan 30, 2019, at
Hi Colin,
I've been running the tests and so far I get the following failures. Are
they known?
kafka.server.ReplicaManagerQuotasTest > shouldGetBothMessagesIfQuotasAllow
FAILED
kafka.server.ReplicaManagerQuotasTest >
testCompleteInDelayedFetchWithReplicaThrottling FAILED
kafka.server.ReplicaManag
Hi Harper,
Thanks for getting back to me-
Well I figured it out eventually, and the clients now failover correctly-
The settings are almost all correct, I needed to change the
"metadata.max.age.ms" setting
It defaults to 5 minutes and I was restarting the brokers within less than one
minute.
B