Re: Issue in Kafka 2.0.0 ?

Sent out a PR #5543 which fixes the reported bug, with StreamToTableJoinScalaIntegrationTestImplicitSerdes.testShouldCountClicksPerRegion modified adding the filter methods. FYI On Mon, Aug 20, 2018 at 5:26 PM Ted Yu wrote: > Thanks for pointing me to that PR. > > I applied the PR locally but

Re: Issue in Kafka 2.0.0 ?

Hi, I am aware that more than one method from KTable.scala have this issue. Once I find a solution, I will apply the fix to the methods you listed. Cheers On Mon, Aug 20, 2018 at 5:23 PM Druhin Sagar Goel wrote: > Thanks a lot Ted! > > FYI - The issue is not limited to the > org.apache.kafka.s

Re: Issue in Kafka 2.0.0 ?

Thanks for pointing me to that PR. I applied the PR locally but still got: org.apache.kafka.streams.scala.StreamToTableJoinScalaIntegrationTestImplicitSerdes > testShouldCountClicksPerRegion FAILED java.lang.StackOverflowError I can go over that PR to see what can be referenced for solving t

Re: Issue in Kafka 2.0.0 ?

Thanks a lot Ted! FYI - The issue is not limited to the org.apache.kafka.streams.scala.KTable.filter. It also happens with org.apache.kafka.streams.scala.KTable.filterNot, org.apache.kafka.streams.scala.KStream.foreach and org.apache.kafka.streams.scala.KStream.peek. - Druhin On August 20,

Re: Issue in Kafka 2.0.0 ?

Is this related to the fix https://github.com/apache/kafka/pull/5502 that is currently being worked on? Guozhang On Mon, Aug 20, 2018 at 5:19 PM, Matthias J. Sax wrote: > Thanks for reporting and for creating the ticket! > > -Matthias > > On 8/20/18 5:17 PM, Ted Yu wrote: > > I was able to rep

Re: Issue in Kafka 2.0.0 ?

Thanks for reporting and for creating the ticket! -Matthias On 8/20/18 5:17 PM, Ted Yu wrote: > I was able to reproduce what you saw with modification > to StreamToTableJoinScalaIntegrationTestImplicitSerdes.scala > I have logged KAFKA-7316 and am looking for a fix. > > FYI > > On Mon, Aug 20,

Re: Issue in Kafka 2.0.0 ?

I was able to reproduce what you saw with modification to StreamToTableJoinScalaIntegrationTestImplicitSerdes.scala I have logged KAFKA-7316 and am looking for a fix. FYI On Mon, Aug 20, 2018 at 1:39 PM Druhin Sagar Goel wrote: > Isn’t that a bug then? Or can I fix my code somehow? > > > > On A

Re: Issue in Kafka 2.0.0 ?

Isn’t that a bug then? Or can I fix my code somehow? On August 20, 2018 at 1:30:42 PM, Ted Yu (yuzhih...@gmail.com) wrote: I think what happened in your use case was that the following implicit from ImplicitConversions.scala kept wrapping the resultant KTable from f

Re: Issue in Kafka 2.0.0 ?

I think what happened in your use case was that the following implicit from ImplicitConversions.scala kept wrapping the resultant KTable from filter(): implicit def wrapKTable[K, V](inner: KTableJ[K, V]): KTable[K, V] = leading to stack overflow. Cheers On Mon, Aug 20, 2018 at 12:50 PM Druhin

Re: Issue in kafka

Hi Subash, First try to check if your zookeeper has your kafka broker registered: /opt/zookeeper/bin/zkCli.sh -server localhost:2181 <<< "ls /brokers/ids" The output should list your brokers. In your case [0]. In my dev env I have 3 brokers. [zk: localhost:2181(CONNECTED) 0] ls /brokers/ids [0

Re: Issue in Kafka running for few days

Ah, yes, you're right. I miss-read it. My bad. Apologies. Michal On 30/04/17 16:02, Svante Karlsson wrote: @michal My interpretation is that he's running 2 instances of zookeeper - not 6. (1 on the "4 broker machine" and one on the other) I'm not sure where that leaves you in zookeeper lan

Re: Issue in Kafka running for few days

@michal My interpretation is that he's running 2 instances of zookeeper - not 6. (1 on the "4 broker machine" and one on the other) I'm not sure where that leaves you in zookeeper land - ie if you happen to have a timeout between the two zookeepers will you be out of service or will you have a sp

Re: Issue in Kafka running for few days

Hi Jan, Correct. As I said before it's not common or recommended practice to run an even number, and I wouldn't recommend it myself. I hope it didn't sound as if I did. However, I don't see how this would cause the issue at hand unless at least 3 out of the 6 zookeepers died, but that could

Re: Issue in Kafka running for few days

I looked this up yesterday when I read the grandparent, as my old company ran two and I needed to know. Your link is a bit ambiguous but it has a link to the zookeeper Getting Started guide which says this: " For replicated mode, a minimum of three servers are required, and it is strongly recomme

Re: Issue in Kafka running for few days

Svante, I don't share your opinion. Having an even number of zookeepers is not a problem in itself, it simply means you don't get any better resilience than if you had one fewer instance. Yes, it's not common or recommended practice, but you are allowed to have an even number of zookeepers and

Re: Issue in Kafka running for few days

You are not supposed to run an even number of zookeepers. Fix that first On Apr 26, 2017 20:59, "Abhit Kalsotra" wrote: > Any pointers please > > > Abhi > > On Wed, Apr 26, 2017 at 11:03 PM, Abhit Kalsotra > wrote: > > > Hi * > > > > My kafka setup > > > > > > **OS: Windows Machine*6 broker

Re: Issue in Kafka running for few days

Any pointers please Abhi On Wed, Apr 26, 2017 at 11:03 PM, Abhit Kalsotra wrote: > Hi * > > My kafka setup > > > **OS: Windows Machine*6 broker nodes , 4 on one Machine and 2 on other > Machine* > > **ZK instance on (4 broker nodes Machine) and another ZK on (2 broker > nodes machine)* > *