Master node crashed throwing "bug" in log

General

Escalation

General

Escalation

Description

Master node in a 4 node cluster crashed this morning after 10 months online with no issues.

Wouldn't restart and in the mysql log kept throwing percona bug alerts. See attached files.

Resolved by dropping master node out of cluster and rejoining as a read only slave to resync.

Environment

Ubuntu 18.10

Attachments

22 Sep 2020, 02:05 PM
04 Sep 2020, 03:37 PM
04 Sep 2020, 03:37 PM

Smart Checklist

Activity

Show:

Jira Bot April 30, 2021 at 9:56 AM

Hello @David Hinchliffe,
It's been 52 days since this issue went into Incomplete and we haven't heard
from you on this.

At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".

Jira Bot April 22, 2021 at 8:56 AM

Hello @David Hinchliffe,
It's jira-bot again. Your bug report is important to us, but we haven't heard
from you since the previous notification. If we don't hear from you on
this in 7 days, the issue will be automatically closed.

Jira Bot April 7, 2021 at 7:56 AM

Hello @David Hinchliffe,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.

Lalit Choudhary March 9, 2021 at 7:39 AM

Hi David,

So I'm unable to reproduce this issue. Can you help us with information that will help us to reproduce this case. Like what operation was running before the crash, any particular operation causing this crash like ALTER/ any other operation.

Also, upgrade to the latest PXC version and see if it fixes the issue.