Skip to:

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

Issues

Select view

Select search mode

 
1 of 1

Orchestrator RestartReplicationQuick fails with Error 1065 (query was empty)

Done

Description

If Orchestrator host can't access Source database, and the Replica is lagging behind, it will call runEmergentOperations, case UnreachableMasterWithLaggingReplicas, and finally will fail when calling RestartReplicationQuick with the following error:

How to repeat:

  1. Deploy latest Percona Orchestrator

  1. You can set the Orchestrator option ReplicationLagQuery to produce lag artificially:

  1. On Source create the status table:

  1. On Source, prevent Orchestrator node from connecting the server:

I also tested using percona-orchestrator-3.2.6-13.el8.x86_64.rpm package and I don't see this issue.

Environment

None

AFFECTED CS IDs

CS0050200

Details

Assignee

Reporter

Labels

Planned Version/s

Needs QA

No

Components

Sprint

Affects versions

Priority

Smart Checklist

Created October 23, 2024 at 12:41 AM
Updated January 14, 2025 at 10:17 AM
Resolved November 8, 2024 at 9:05 AM

Activity

Kamil HolubickiNovember 8, 2024 at 9:05 AM

Will be fixed by DISTMYSQL-466