5.7.mysql_aurora.2.07.0 randomly crashes with mysqld got signal 11

0

We just switched a MySQL host to Aurora using the new 5.7.mysql_aurora.2.07.0 version. It ran fine overnight but this morning we started getting random crashes. We will get one or two and then it will be fine for a few hours and then we will get a few more and so on.

These are the logs:
20:55:19 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

20:55:19 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

We are running Aurora on other databases with very similar workloads and queries with no problems. The only difference between them is that we are running 5.7.12 instead of 5.7.mysql_aurora.2.07.0.

Initially, this seems like an issue on the newer version. Any help is appreciated.

gbird
已提問 4 年前檢視次數 621 次
2 個答案
0

Hi,

I have a similar problem.
{message:id=925727}

I hope this problem will be resolved as quickly as possible.

null
已回答 4 年前
0

AWS released a new version of aurora 2.07.1 that is supposed to fix this. We have not upgrade yet as we used DMS to downgrade the instance instead.

gbird
已回答 4 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南