PITR has errors "scan binlogs: sql: expected 2 destination arguments in Scan, not 3"

I’ve rolled out a new cluster, integrated Google bucket storage in S3 mode, done a manual backup without any issue, and am now trying to get PITR to S3 working, but I keep getting this error from the PITR pod:

2021/05/18 13:50:08 ERROR: get binlog time get binlog list for host lithium-pxc-0.lithium-pxc.percona.svc.cluster.local: scan binlogs: sql: expected 2 destination arguments in Scan, not 3
2021/05/18 13:50:08 ERROR: get binlog time get binlog list for host lithium-pxc-1.lithium-pxc.percona.svc.cluster.local: scan binlogs: sql: expected 2 destination arguments in Scan, not 3
2021/05/18 13:50:08 ERROR: get binlog time get binlog list for host lithium-pxc-2.lithium-pxc.percona.svc.cluster.local: scan binlogs: sql: expected 2 destination arguments in Scan, not 3
2021/05/18 13:50:08 ERROR: new db connection: get host: can’t find host

binary logging is definately enabled:

BMySQL [lithium_accounting_internal]> SHOW BINARY LOGS;
±----------±-----------+
| Log_name | File_size |
±----------±-----------+
| ON.000001 | 1074370202 |
| ON.000002 | 1074262473 |
| ON.000003 | 1074567455 |
| ON.000004 | 1074773930 |
| ON.000005 | 1074377427 |
| ON.000006 | 1074027489 |
| ON.000007 | 232224147 |
±----------±-----------+

BMySQL [lithium_accounting_internal]> show master status;
±----------±----------±-------------±-----------------±------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
±----------±----------±-------------±-----------------±------------------+
| ON.000007 | 232224147 | | | |
±----------±----------±-------------±-----------------±------------------+

Cluster is ready and working, everything is in sync, just dont know whats going on here with PITR.

Thanks in advance,

K

1 Like

I saw your message in discord. Seems you are running MySQL 5.7. PITR is supported in 8.0 for now as per https://www.percona.com/doc/kubernetes-operator-for-pxc/backups.html#storing-binary-logs-for-point-in-time-recovery:

Point-in-time recovery is off by default and is supported by the Operator only with Percona XtraDB Cluster versions starting from 8.0.21-12.1.

1 Like

Hi @spronin 100% correct yes,

I will be upgrading my cluster shortly, just waiting to upgrade my database connection pools to Hikari in our java apps first.

Thanks for the response.

1 Like