MySQL Bugs: #95295: Node crashing randomly

Bug #95295	Node crashing randomly
Submitted:	8 May 2019 11:40	Modified:	9 Jun 2019 14:55
Reporter:	Guillaume FRANCOIS	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	mysql-5.7.26 ndb-7.6.10	OS:	Ubuntu (18.04 LTS bionic)
Assigned to:	MySQL Verification Team	CPU Architecture:	x86

Description:
MySQL cluster data nodes are crashing randomly. Sometime even during the start (after crash) of the node.

How to repeat:
As it as random, we don't know how to reproduce.

Node error log file

Attachment: ndb_33_error.log (application/octet-stream, text), 20.53 KiB.

Node trace file

Attachment: ndb_33_trace.log.21 (application/octet-stream, text), 1.21 MiB.

Node trace file

Attachment: ndb_33_trace.log.21_t1 (application/octet-stream, text), 1.01 MiB.

Node trace file

Attachment: ndb_33_trace.log.21_t2 (application/octet-stream, text), 1.59 MiB.

Node trace file

Attachment: ndb_33_trace.log.21_t3 (application/octet-stream, text), 880.38 KiB.

Node out log file

Attachment: ndb_33_out.log (application/octet-stream, text), 2.87 MiB.

Node trace file

Attachment: ndb_33_trace.log.17 (application/octet-stream, text), 1.34 MiB.

Node trace file

Attachment: ndb_33_trace.log.17_t1 (application/octet-stream, text), 1.05 MiB.

Node trace file

Attachment: ndb_33_trace.log.17_t2 (application/octet-stream, text), 1.50 MiB.

Node trace file

Attachment: ndb_33_trace.log.17_t3 (application/octet-stream, text), 896.36 KiB.

Version detail:
* name: Linux - Generic (glibc 2.12) (x86, 64-bit), Compressed TAR Archive 	
* version: 7.6.10
* package size:	873.1M 	
* archive name: mysql-cluster-gpl-7.6.10-linux-glibc2.12-x86_64.tar.gz

Hi,
I cant see any pattern in whats happening to your system. You need to provide more data about your system and a way to reproduce the crash. 

thanks
Bogdan

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".