Hello!
If it's always the same physical machine, I would check hardware and/or OS.
I don't remember seeing this exception and I don't see why you would only
see it on 1 node.
Regards,
--
Ilya Kasnacheev
пн, 20 янв. 2020 г. в 11:50, tarunk <tarun.swprofessio...@gmail.com>:
> Hi All,
>
> In our 12 nodes ignite cluster one of the node jvm get crashes sometimes
> with below error.
> Is this some know issue with Ignite ? or some other memory/jvm issue.
> We are using openjdk 1.8 ("1.8.0_232") provided by RedHat.
>
> A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fef7f1d3eb0, pid=42623,
> tid=0x00007feea62c8700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build
> 1.8.0_222-b10)
> # Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64
> compressed oops)
> # Problematic frame:
> # J 62683 C2
>
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(Ljava/lang/Object;)V
> (331 bytes) @ 0x00007fef7f1d3eb0 [0x00007fef7f1d3e00+0xb0]
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core
> dumping, try "ulimit -c unlimited" before starting Java again
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
