Skip to:

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

Issuing rollback() due to DESTROY without explicit disconnect() of DBD::mysql::db handle

Description

This started happening with previous releases with mysql and percona-toolkit and has remained even with newer releases.

Not sure if there is a way to have pt-table-checksum retry these tables when it fails like this. Nothing has changed with my db servers except new percona releases.

Environment

percona-release 1.0-21.generic

percona-server-client 8.0.34-26-1.buster

percona-server-common 8.0.34-26-1.buster

percona-server-server 8.0.34-26-1.buster

percona-toolkit 3.5.5-1.buster

percona-xtrabackup-80 8.0.35-30-1.buster

Activity

Show:

matthew December 28, 2023 at 3:34 PM

Added details to the existing bug. Thanks!

Aaditya Dubey December 28, 2023 at 12:42 PM

Hi ,

We are already tracking this case here but unfortunately not able to repeat, Please share exact steps which clould be helpful to repeat the issue and we are closing this report as duplicate.

matthew December 27, 2023 at 2:57 PM

percona-toolkit 3.5.7-1.buster is still exhibiting the same behavior.

Duplicate

Details

Assignee

Reporter

Priority

Components

Affects versions

Needs QA

Yes

Smart Checklist

Created December 13, 2023 at 1:31 PM
Updated December 28, 2023 at 3:34 PM
Resolved December 28, 2023 at 12:43 PM