Skip to content

Conversation

@ynnt
Copy link

@ynnt ynnt commented Oct 23, 2020

closes/fixes #613

  • I've made sure the Changelog.md will remain up-to-date after this PR is merged.

@ynnt ynnt force-pushed the reset-master-replication branch from 7cf1385 to 859eaf8 Compare October 23, 2020 13:37
@ynnt
Copy link
Author

ynnt commented Oct 27, 2020

@AMecea is there a chance to get this merged in?

@AMecea
Copy link
Contributor

AMecea commented Oct 27, 2020

Hi @ynnt, thank you for your contribution, I have other thoughts about this, to let the Orchestrator handle this and drop this support from operator. I will be back with more information shortly.

@ynnt
Copy link
Author

ynnt commented Nov 3, 2020

Any suggestions for the direction @AMecea ? I can dedicate some time to make it happen as this issue is super annoying

@AMecea
Copy link
Contributor

AMecea commented Nov 3, 2020

I agree, I didn't manage to do a detailed plan yet, it's related to #522 but slightly different. I've opened a new issue (#627) and we can discuss it there. If we conclude that the current implementation of readOnly is ok then we can merge this otherwise this will not be used.

@jianhaiqing
Copy link
Contributor

I agree that this should be done by orchestrator. Operator is not supposed to handle the failover process.

@ynnt ynnt closed this Apr 13, 2021
@chengliangela
Copy link

I am also running into the same problem.Do you know when to solve the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New master is not replicating after a failover

4 participants