Re: SIGSEGV (0xb) on TransactionCoordinator

2018-12-27 Thread wenxing zheng
Hi Peter, we didn't upgrade the JDK8, but just remove the G1GC. And now it seemed stable, but we need to keep monitoring the status to finally confirm. Kind Regards, Wenxing On Thu, Dec 27, 2018 at 9:43 PM Peter Levart wrote: > Here's a report on the Jira with exactly the same crash and the rep

Re: How does the /tmp/kafka-streams folder work?

2018-12-27 Thread Matthias J. Sax
All data is backed in the Kafka cluster. Data that is stored locally, is basically a cache, and Kafka Streams will recreate the local data if you loose it. Thus, I am not sure how the KTable data could be stale. One possibility might be a miss-configuration: I assume that you read the topic direct

Re: Kafka tests on a remote cluster

2018-12-27 Thread Parviz deyhim
+d...@kafka.apache.org On Wed, Dec 26, 2018 at 8:53 PM Parviz deyhim wrote: > Thanks fair points. Probably best if I simplify the question: How does > Kafka community run tests besides using mocked local Kafka components? > Surely there are tests to confirm different failure scenarios such as >

Re: stream shutdown error

2018-12-27 Thread Matthias J. Sax
I am not 100% sure what you exactly do to upgrade to 2.1. But if you add a `suppress()` operator, you change your topology and therefore the old and new program is not compatible any longer. To avoid breaking changes like this, you can now (since 2.1) name all operators, stores, and changelog topi

stream shutdown error

2018-12-27 Thread 徐华
Hi, I am use kafka stream new feature in kafka. My kafka vision : 2.0 My kafka-client vision : 2.1 But i can use the new feature : KIP-328-Final window results per key

Kafka client troubles when restarting a broker

2018-12-27 Thread Andrey Dyachkov
Hi guys, When broker goes down due to restart, running and new consumers starting to fail with: [Consumer clientId=consumer-42169, groupId=] Connection to node 67108872 could not be established. Broker may not be available. [Consumer clientId=consumer-46213, groupId=] Connection to node -4 could n

Re: two consumers in same consumer group get same messages

2018-12-27 Thread Peter Levart
Hi, On 12/26/18 10:53 AM, MCG wrote: I'm not talking about orderliness, but that the same consumer group, the same partition, is consumed by multiple consumers. I use kafka-consumer-groups.sh and org.apache.kafka.clients.admin.AdminClient to validate the results. Because the same consumer gro

Re: SIGSEGV (0xb) on TransactionCoordinator

2018-12-27 Thread Peter Levart
Here's a report on the Jira with exactly the same crash and the reported was using the same JDK 8u92... https://issues.apache.org/jira/browse/KAFKA-7625 ...the reporter upgraded to latest JDK 8 and it seems to be stable since then. Regards, Peter On 12/27/18 11:29 AM, wenxing zheng wrote:

Re: SIGSEGV (0xb) on TransactionCoordinator

2018-12-27 Thread Peter Levart
Hi, G1 has had lots of fixes since 8u92 until latest 8u192. If you can (Kafka 2.1.0 has been certified to work with JDK 11), you could even try to use JDK 11 (if your other libraries allow you to, of course). G1 has had lots of improvements on JDK 11 since JDK 8 too... Regards, Peter On 12/

Re: SIGSEGV (0xb) on TransactionCoordinator

2018-12-27 Thread wenxing zheng
Thanks to Peter. We did a lot of tests today, and found that the issue will happen after enabling G1GC. If we go with default settings, everything looks fine. On Thu, Dec 27, 2018 at 4:49 PM Peter Levart wrote: > Hi, > > It looks like a JVM bug. If I were you, 1st thing I'd do is upgrading > th

Re: SIGSEGV (0xb) on TransactionCoordinator

2018-12-27 Thread Peter Levart
Hi, It looks like a JVM bug. If I were you, 1st thing I'd do is upgrading the JDK to the latest JDK8u192. You're using JDK8u92 which is quite old (2+ years)... Regards, Peter On 12/27/18 3:53 AM, wenxing zheng wrote: Dear all, We got a coredump with the following info last night, on this e