hello，I have done a series of tests on kafka 0.9.0，and one of the results
confused me.
test enviroment:
kafka cluster: 3 brokers，8core cpu ／ 8g mem ／1g netcard
client：4core cpu／4g mem
topic：6 partitions，2 replica
total messages：1
singal message size：1024byte
Thanks for validating!
Guozhang
On Fri, Jun 17, 2016 at 7:39 PM, Tim Renner
wrote:
> Hi Guozhang,
>
> Apologies for the delay - had to convert to the new groupBy. The fix got
> rid of the error.
>
> Thanks!
>
> Tim
>
--
-- Guozhang
Hi Guozhang,
Apologies for the delay - had to convert to the new groupBy. The fix got
rid of the error.
Thanks!
Tim
Hello Tim,
I think I found the issue, could you apply the following patch and retry
your app?
https://github.com/apache/kafka/pull/1520
Guozhang
On Thu, Jun 16, 2016 at 11:11 PM, Guozhang Wang wrote:
> Hello Tim,
>
> By looking through the source code I suspect it is a bug in Kafka Stream's
Does anybody have good RHEL 7 systemd scripts for the broker, zookeeper, schema
registry, etc ... ?
This e-mail and any files transmitted with it are confidential, may contain
sensitive information, and are intended solely for the use of the individual or
entity to whom they are addressed. If
Hi Harsha,
Comments below.
On Fri, Jun 17, 2016 at 7:48 PM, Harsha wrote:
> Hi Ismael,
> "Are you saying that you are aware of many Kafka users still
> using Java 7
> > who would be ready to upgrade to the next Kafka feature release (whatever
> > that version number is) before t
If you have a consumer listening on a topic and that topic is deleted is
the consumer made aware -- perhaps by some exception -- or does it
continue listening, blissfully unaware that it will never hear anything
more?
Thanks,
Chris
Hi Ismael,
"Are you saying that you are aware of many Kafka users still
using Java 7
> who would be ready to upgrade to the next Kafka feature release (whatever
> that version number is) before they can upgrade to Java 8?"
I know there quite few users who are still on java 7 and reg
Did you check if the controller is active in the cluster? If the controller
isn't active (there are known 0.8 bugs that can lead to this), then this
could cause this kind of data loss issue. I recommend upgrading to 0.9 ASAP.
Thanks
Tom Crayford
Heroku Kafka
On Friday, 17 June 2016, Gulia, Vikra
+1
We can't promise security features whilst using a deprecated version of the
JDK and relying on it for underlying security functionality (e.g. SSL).
This impacts both clients and brokers. Java 7 has been deprecated for over
a year, and software that isn't up to date with that is at fault with
re
Hi.
I am trying to use an embedded Kafka server to allow me to create tests in
jUnit using a real Kafka implementation, instead of a stub or a mock.
I am using Kafka version 0.9.0.0.
The test works, but the consumer poll has to wait for 3 seconds to get the
message.
Here is the code I am runnin
I also think that Kafka should drop java 7 and scala 2.10 already.
However, I expect Kafka (or any other project) to do it in two steps:
1. announce NOW that both of them are deprecated in the 0.10 series and
will be dropped in the next major release.
2. drop them a the next major release.
(ideall
Thank you for your thorough explanation Michael. It helped a lot.
Cheers
Davood
On Thu, Jun 16, 2016 at 5:01 PM, Michael Noll wrote:
> Davood,
>
> you are reading the input topic into a KTable, which means that subsequent
> records for the same key (such as the key `1`, which appears twice in t
Hello,
I'm currently working with kafka 0.10.0.0 in Java 8 and facing the
following issue:
When I create multiple topics with the AdminUtil one by one and
immediately start an KafkaConsumer (subscribed to this topic) in a new
thread, many (not all) KafkaConsumers do not receive any messages
Hi Gerard, thanks for the reply. Few follow ups -
1. I can try setting acks = all but wouldn't it lead to performance hit (I
am using sync produce thus response time will be more).
2. I will try unclean.leader.election.enable = false and update you if it
helps.
3. Regarding your last point, I am c
My guess is that say your broker went down and you restarted it.
That time interval between shutdown/crash and the restart was shorter than the
ZK node's ephemeral timeout value.
Once that time is over, your node disappears from Zookeeper, the broker is able
to recreate the znode and hence the s
Hi Marcus,
Thanks for your feedback.
With regards to IBM WebSphere, the latest stable release (8.5.5) supports
Java 8 according to the documentation:
http://www-01.ibm.com/support/docview.wss?uid=swg27005002
Having said that, it is fair to discuss servers and clients separately. In
Kafka, you c
Compatibility shouldn't be broken in a minor release. Minor versions are
for new features in a backwards-compatible manner. The Kafka bylaws do not
explicitly state this but I believe it is implied based on general practice
and so many other Apache projects explicitly calling this out, documenting
On Fri, 17 Jun 2016, 14:41 Gerard Klijs, wrote:
> What do you mean with a *docker volume*?
The container is started through docker-compose, using the VOLUMES keyword
to mount the folder where Kafka saves the log.
I'm running all of this on windows using the standard distribution of
docker for w
Scala 2.12 requires JDK 8 to take advantage of JVM technology. Forcing
migration to JDK 8 explains to some extent the non rush to release 2.12. I
believe Adriaan Moors has a presentation detailing the 2.12 Scala release.
https://adriaanm.github.io/reveal.js/scala-next.html#/
On 17 Jun 2016 8:35 a.m
+1 - wish it was already done with Kafka 0.9 version :)
From: Tommy Becker
To: users@kafka.apache.org
Sent: Friday, June 17, 2016 7:55 AM
Subject: Re: [DISCUSS] Java 8 as a minimum requirement
+1 We're on Java 8 already.
On 06/16/2016 04:45 PM, Ismael Juma wrote:
Hi all,
I would
Try mounting it to /tmp/ then you will see if it's a file permission issue.
On Fri, Jun 17, 2016 at 1:27 PM, Gerard Klijs
wrote:
> What do you mean with a *docker volume*? It's best to use a data container,
> and use the volumes in your broker container, this way you can destroy the
> broker con
What do you mean with a *docker volume*? It's best to use a data container,
and use the volumes in your broker container, this way you can destroy the
broker container without affecting the data. The data container itself
needs to be configured depending on the host. For example when the host is
ru
On Thu, Jun 16, 2016 at 5:20 PM, Ismael Juma wrote:
> On Thu, Jun 16, 2016 at 11:13 PM, Stephen Boesch
> wrote:
>
> > @Jeff Klukas What is the concern about scala 2.11 vs 2.12? 2.11 runs on
> > both java7 and java8
> >
>
> Scala 2.10.5 and 2.10.6 also support Java 8 for what it's worth.
>
I w
That would be very doubtful imho. It is much more adventurous to go latest
Kafka release than to go JDK 8.
On 17 Jun 2016 3:19 a.m., "Ismael Juma" wrote:
> Hi Harsha,
>
> Are you saying that you are aware of many Kafka users still using Java 7
> who would be ready to upgrade to the next Kafka fea
+1 We're on Java 8 already.
On 06/16/2016 04:45 PM, Ismael Juma wrote:
Hi all,
I would like to start a discussion on making Java 8 a minimum requirement
for Kafka's next feature release (let's say Kafka 0.10.1.0 for now). This
is the first discussion on the topic so the idea is to understand ho
I totally agree with Marcus.
No issue in upgrading the broker's code to 8.
For the client, there can be lots of users which are required to stay 7
because of dependencies.
So, stay with 7 at least for the client.
And... if you break compatibility to 7 please do that in a major release.
*Valeri
Hello people,
I'm running one single kafka broker from within a docker container. The
folder where kafka writes the logs is mounted as *docker volume* on my
system.
As soon as I try to create a topic I get this error
[2016-06-15 10:22:53,602] ERROR [KafkaApi-0] Error when handling request
{contr
I am using Kafka 0.9.0.1 with ZK 3.5.0-alpha
I am seeing this error intermittently which goes away after several reboots.
Any ideas?
Sent from my iPad
Hello!
I would like to know what are the configurations/properties for the
producer/consumer in order fail fast when the connection to the entire
broker cluster is lost.
For example if we can set up a parameter that when the connection trial
reached a treshold then disconnect and throw an excepti
+1 we already use java 8
On Fri, Jun 17, 2016 at 11:07 AM Jaikiran Pai
wrote:
> +1 for Java 8. Our eco-system which uses Kafka and many other open
> source projects are now fully on Java 8 since a year or more.
>
> -Jaikiran
> On Friday 17 June 2016 02:15 AM, Ismael Juma wrote:
> > Hi all,
> >
>
+1 for Java 8. Our eco-system which uses Kafka and many other open
source projects are now fully on Java 8 since a year or more.
-Jaikiran
On Friday 17 June 2016 02:15 AM, Ismael Juma wrote:
Hi all,
I would like to start a discussion on making Java 8 a minimum requirement
for Kafka's next feat
I agree with Harsha and Marcus. Many of the kafka users are still on java 7
and
some of them definitely upgrade to newer versions. We may need to support
for a while.
We can remove the support from next major version onwards.
Thanks,
Manikumar
On Fri, Jun 17, 2016 at 2:04 PM, Marcus Gründler wr
+1 on Java 8 already, Scala 2.11 is enough as well
On Fri, Jun 17, 2016 at 9:48 AM, Achanta Vamsi Subhash <
achanta.va...@flipkart.com> wrote:
> +1 to Java8 - we have already moved to Java8 last year.
>
> On Fri, Jun 17, 2016 at 12:48 PM, Ismael Juma wrote:
>
> > Hi Harsha,
> >
> > Are you sayin
-1
Hi Ismael,
Although I really like the Java 8 features and understand the advantages you
mentioned about Java 8 migration, I would suggest to stay with Java 7 as
a minimum requirement for a while.
I think there are two aspects to consider - Kafka Server and Kafka clients. On
the server part it
Hi,
Sorry for posting twice. It seems the issue I have encountered is indeed
https://issues.apache.org/jira/browse/KAFKA-3129 as indicated by Vahid
Hashemian in the other thread. If I change request.required.acks to 1 it
works fine.
As far as the problem going away if the broker is started a long
+1 to Java8 - we have already moved to Java8 last year.
On Fri, Jun 17, 2016 at 12:48 PM, Ismael Juma wrote:
> Hi Harsha,
>
> Are you saying that you are aware of many Kafka users still using Java 7
> who would be ready to upgrade to the next Kafka feature release (whatever
> that version number
Hi Harsha,
Are you saying that you are aware of many Kafka users still using Java 7
who would be ready to upgrade to the next Kafka feature release (whatever
that version number is) before they can upgrade to Java 8?
The 0.10.1 versus 0.11.0.0 is something that can be discussed separately as
no d
Great!
Ismael
On Fri, Jun 17, 2016 at 2:26 AM, Philippe Derome wrote:
> Thanks a lot for that. I must had done something wrong.
>
> I reinstalled gradle on OSX 10.11 using MacPorts, then recloned kafka and
> then followed the normal steps and it worked just fine.
>
> On Thu, Jun 16, 2016 at 6:4
39 matches
Mail list logo
