You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Vishnu Viswanath <vi...@gmail.com> on 2018/10/16 01:34:36 UTC
SIGSEGV fault in Kafka broker
Hello Kafka experts,
I am running Kafka version 1.1.0 in docker container and the container is
exiting with SIGSEGV.
The container is running with 32gb memory limit and 1Gb Xmx for Kafka
process.
I see following in the core dump:
Current thread:
=>0x0000562f20d65000 JavaThread "pool-4-thread-1" [_thread_in_Java, id=427,
stack(0x00007f819c429000,0x00007f819c529aa8)]
RBP=0x00000000fff00750 is an oop
org.apache.kafka.common.utils.PureJavaCrc32C
- klass: 'org/apache/kafka/common/utils/PureJavaCrc32C'
Does it mean that PureJavaCrc32C is accessing an invalid memory location?
What could be the reason for this?
Has anyone else faced this issue before? Is there any chance that this
could happen because kafka is running OOM.
Thanks,
Vishnu
Re: SIGSEGV fault in Kafka broker
Posted by Ismael Juma <is...@gmail.com>.
It's probably because you're using Alpine Linux. That's not a supported
operating system as we don't test with it.
Ismael
On Tue, 16 Oct 2018, 11:50 Vishnu Viswanath, <vi...@gmail.com>
wrote:
> Hi,
>
> I am using openjdk-jre 8.
> https://pkgs.alpinelinux.org/package/v3.6/community/x86/openjdk8-jre
>
> I also noticed that this error occurs when Kafka tries to rebuild corrupt
> indices.
> The code flow looks like this :
> ProduceraStateManager.readSnapshot() -> Crc32C.compute() -> SIGSEGV
>
> Thanks,
> Vishnu
>
> On Tue, Oct 16, 2018 at 11:19 AM Ismael Juma <is...@juma.me.uk> wrote:
>
> > Looks like a JVM bug. What Java distribution and version are you using?
> >
> > Ismael
> >
> > On Mon, Oct 15, 2018 at 6:34 PM Vishnu Viswanath <
> > vishnu.viswanath25@gmail.com> wrote:
> >
> > > Hello Kafka experts,
> > >
> > > I am running Kafka version 1.1.0 in docker container and the container
> is
> > > exiting with SIGSEGV.
> > > The container is running with 32gb memory limit and 1Gb Xmx for Kafka
> > > process.
> > >
> > > I see following in the core dump:
> > > Current thread:
> > > =>0x0000562f20d65000 JavaThread "pool-4-thread-1" [_thread_in_Java,
> > id=427,
> > > stack(0x00007f819c429000,0x00007f819c529aa8)]
> > >
> > > RBP=0x00000000fff00750 is an oop
> > > org.apache.kafka.common.utils.PureJavaCrc32C
> > > - klass: 'org/apache/kafka/common/utils/PureJavaCrc32C'
> > >
> > > Does it mean that PureJavaCrc32C is accessing an invalid memory
> location?
> > > What could be the reason for this?
> > >
> > > Has anyone else faced this issue before? Is there any chance that this
> > > could happen because kafka is running OOM.
> > >
> > > Thanks,
> > > Vishnu
> > >
> >
>
Re: SIGSEGV fault in Kafka broker
Posted by Vishnu Viswanath <vi...@gmail.com>.
Hi,
I am using openjdk-jre 8.
https://pkgs.alpinelinux.org/package/v3.6/community/x86/openjdk8-jre
I also noticed that this error occurs when Kafka tries to rebuild corrupt
indices.
The code flow looks like this :
ProduceraStateManager.readSnapshot() -> Crc32C.compute() -> SIGSEGV
Thanks,
Vishnu
On Tue, Oct 16, 2018 at 11:19 AM Ismael Juma <is...@juma.me.uk> wrote:
> Looks like a JVM bug. What Java distribution and version are you using?
>
> Ismael
>
> On Mon, Oct 15, 2018 at 6:34 PM Vishnu Viswanath <
> vishnu.viswanath25@gmail.com> wrote:
>
> > Hello Kafka experts,
> >
> > I am running Kafka version 1.1.0 in docker container and the container is
> > exiting with SIGSEGV.
> > The container is running with 32gb memory limit and 1Gb Xmx for Kafka
> > process.
> >
> > I see following in the core dump:
> > Current thread:
> > =>0x0000562f20d65000 JavaThread "pool-4-thread-1" [_thread_in_Java,
> id=427,
> > stack(0x00007f819c429000,0x00007f819c529aa8)]
> >
> > RBP=0x00000000fff00750 is an oop
> > org.apache.kafka.common.utils.PureJavaCrc32C
> > - klass: 'org/apache/kafka/common/utils/PureJavaCrc32C'
> >
> > Does it mean that PureJavaCrc32C is accessing an invalid memory location?
> > What could be the reason for this?
> >
> > Has anyone else faced this issue before? Is there any chance that this
> > could happen because kafka is running OOM.
> >
> > Thanks,
> > Vishnu
> >
>
Re: SIGSEGV fault in Kafka broker
Posted by Ismael Juma <is...@juma.me.uk>.
Looks like a JVM bug. What Java distribution and version are you using?
Ismael
On Mon, Oct 15, 2018 at 6:34 PM Vishnu Viswanath <
vishnu.viswanath25@gmail.com> wrote:
> Hello Kafka experts,
>
> I am running Kafka version 1.1.0 in docker container and the container is
> exiting with SIGSEGV.
> The container is running with 32gb memory limit and 1Gb Xmx for Kafka
> process.
>
> I see following in the core dump:
> Current thread:
> =>0x0000562f20d65000 JavaThread "pool-4-thread-1" [_thread_in_Java, id=427,
> stack(0x00007f819c429000,0x00007f819c529aa8)]
>
> RBP=0x00000000fff00750 is an oop
> org.apache.kafka.common.utils.PureJavaCrc32C
> - klass: 'org/apache/kafka/common/utils/PureJavaCrc32C'
>
> Does it mean that PureJavaCrc32C is accessing an invalid memory location?
> What could be the reason for this?
>
> Has anyone else faced this issue before? Is there any chance that this
> could happen because kafka is running OOM.
>
> Thanks,
> Vishnu
>