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년 전620회 조회
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년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠