kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ismael Juma <ism...@juma.me.uk>
Subject Re: SIGSEGV fault in Kafka broker
Date Tue, 16 Oct 2018 18:19:17 GMT
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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message