Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
7 of 7

[WSREP-SST] 2022/01/11 18:06:20 socat[23163] E connect(7, AF=2 10.233.86.195:4444, 16): Connection timed out"}]

Incomplete

Description

First of all, I just wanted to report an issue for your awareness. Not expecting to fix it as I already solved it. May help others in the future too.

If you have any bet on what was happened that would be awesome, otherwise please feel free to close it.

Okay, I have a working PXC operator for a year with 3 nodes and experienced an issue recently.

It could be related with pxc-backup.

Here is what I did:

1) I removed a disk from MinIO. So this service was left running, but obviously not working for some time. It was not possible to push backups to it. This was expected.

2) After some hours XtraDB cluster failed with the errors attached.

I had to do a crash recovery as described in https://www.percona.com/doc/kubernetes-operator-for-pxc/recovery.html

Recovered successfully.

3) After several hours issue repeated

The issue lasted until I removed this block from pxc:

pxc-0

pxc-1

pxc-2

Environment

None

Smart Checklist

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Smart Checklist

Created January 13, 2022 at 10:32 PM
Updated March 22, 2024 at 11:28 AM
Resolved March 22, 2024 at 11:27 AM

Activity

Aaditya DubeyMarch 22, 2024 at 11:27 AM

Hi

We still haven't heard any news from you. So, I assume the issue no longer persists and will close the ticket. If you disagree, reply and create a follow-up new Jira Ticket.

Slava SarzhanMarch 14, 2023 at 12:33 PM

Hi do you have any update?

LaimisSeptember 3, 2022 at 3:22 PM

I've got this full pxc crash again. Yeah, I have to update operator and enable backup. This would test exactly same pxc and external conditions, but with latest operator. It would be right test. I have added this task to do list and will test in a while.

Slava SarzhanAugust 17, 2022 at 1:35 PM

Did you try to update your operator ? Can you reproduce this issue using the latest version of operator?

LaimisJune 15, 2022 at 12:58 PM

Many thanks. Unfortunately, I can afford some time to focus on upgrades (maybe code investigation), to be honest. That's for a while. As I found the solution to remove "backup" block in these cases, it's okay. Will never catch the same issue.

I will keep checking release notes from time to time, anything that is availability and performance related are bonus to do go ahead with upgrade.

Keep up the good work.

If anything needed, please get in touch.