Skip to:

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

Switching between group and async replication not working

Description

1. GROUP REPLICATION TO ASYNC
If we switch from group to async replication, deployment and services for the router are left running.

2. ASYNC TO GROUP REPLICATION
Orchestrator stateful set and services are left, but the second mysql pod also gets stuck and will not get ready because of readiness probe issue.

Readiness probe issue:

mysql log:

Environment

None

Smart Checklist

Activity

Show:

Sergey Pronin August 26, 2022 at 10:59 AM

Just to put some context of "On hold" status - it is not a critical issue. Switching between replication topologies is not a common task and it is something that should be picked at the deployment stage.

 

On the other hand, , we will need to explicitly document that changing the topology is not supported by the Operator. Maybe add a protection into the Operator to block such changes.

Details

Assignee

Reporter

Labels

Needs QA

Yes

Affects versions

Priority

Smart Checklist

Created June 29, 2022 at 1:57 PM
Updated February 29, 2024 at 8:12 PM