This message was deleted.
# general
s
This message was deleted.
p
Could you please share the complete core dump file?
v
unfortunately the pod got restarted and the log file as well as the coredump was lost.
we were able to reproduce this most of the time. maxMessageSize is increased to 16MB have incorporated liveliness/readiness probe (When we were doing it without the liveliness/rediness probe the broker sustain the load)
p
Ok, maybe you can share your reproduce step here, so that we can understand more about the issue.
v
Set up pulsar in cluster mode (3 broker, bookie, zookeeper) and pulsar proxy Producer/consumer in shared mode. Message size ~500Kb Load ~200 tps hosted on kubernetes with liveliness/readiness for autoscaling. During load test liveliness/readyness fails and at the same time got the mentioned error.
pod memory 9-14g CPU -2-4 Core
p
Wow, interesting. Does the liveliness/readyness get a timeout error? Maybe you can try to take a thread dump if the liveliness/readyness get failed before the broker restarts
v
as the K8 terminate the pods we need to stop argo cd and test. We are doing that to capture that.
👌 1
r
hello everyone, i too got a similar logs when trying to process pulsar using my java application
Copy code
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000003e6e, pid=1, tid=0x00007f4389f8cb10
#
# JRE version: OpenJDK Runtime Environment (8.0_212-b04) (build 1.8.0_212-b04)
# Java VM: OpenJDK 64-Bit Server VM (25.212-b04 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 3.12.0
# Distribution: Custom build (Sat May  4 17:33:35 UTC 2019)
# Problematic frame:
# C  0x0000000000003e6e
#
# Core dump written. Default location: //core or core.1
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   <https://icedtea.classpath.org/bugzilla>
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  T H R E A D  ---------------

Current thread (0x000055f3fe4cd800):  JavaThread "http-nio-8091-exec-2" daemon [_thread_in_native, id=106, stack(0x00007f4389e8c000,0x00007f4389f8cad0)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000003e6e
the rest of the log file is there where registers , top of the stack etc are captured. is it possible to know what might cause this issue