GC really solved the
> >>>> problem.
> >>>>> Unfortunately I faced that issue last night.
> >>>>>
> >>>>> And what do you mean by " remove the G1GC"? How did you do that?
> >>>>>
> >>>>> Thanks!
mean by " remove the G1GC"? How did you do that?
Thanks!
-Original Message-
From: wenxing zheng [mailto:wenxing.zh...@gmail.com]
Sent: 28 grudnia 2018 04:05
To: Peter Levart
Cc: users@kafka.apache.org
Subject: Re: SIGSEGV (0xb) on TransactionCoordinator
Hi Peter, we didn
the
> > > problem.
> > > > Unfortunately I faced that issue last night.
> > > >
> > > > And what do you mean by " remove the G1GC"? How did you do that?
> > > >
> > > > Thanks!
> > > >
> > > >
> > &
> >
> > > And what do you mean by " remove the G1GC"? How did you do that?
> > >
> > > Thanks!
> > >
> > >
> > >
> > > -Original Message-----
> > > From: wenxing zheng [mailto:wenxing.zh...@gmail.com]
> > > Sent: 28 grudn
sue last night.
> >
> > And what do you mean by " remove the G1GC"? How did you do that?
> >
> > Thanks!
> >
> >
> >
> > -Original Message-
> > From: wenxing zheng [mailto:wenxing.zh...@gmail.com]
> > S
eter Levart
> Cc: users@kafka.apache.org
> Subject: Re: SIGSEGV (0xb) on TransactionCoordinator
>
>
>
> 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.
>
>
>
&
.com]
Sent: 28 grudnia 2018 04:05
To: Peter Levart
Cc: users@kafka.apache.org
Subject: Re: SIGSEGV (0xb) on TransactionCoordinator
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.
Ki
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
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:
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
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
>
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
Dear all,
We got a coredump with the following info last night, on this environment,
we enable the
transaction. Please kindly advice what would be the problem here.
#
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x7f546a857d0d, pid=13288,
13 matches
Mail list logo
