percona / percona/pxc_scheduler_handler
Isolation of actions done by multiple concurrent schedulers
@Tusamarco is already working on this.
Since Jun 27, 2021.
- Dominant language
- Go
- Stars
- 15
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
In case we have multiple instance of Handler running in the same ProxySQL handling different set of servers, when one of them needs to apply a status change, a possible clash/conflict can exists.
This because changes to memory stage tables in ProxySQL are seen immediately by other threads, and so doing LOAD...TO RUNTIME from handler 1 could be loading half-baked changes done by handler 2.
As such the whole table is refreshed and modified. To prevent the conflict a lock should exists that will avoid to have two Handler committing the changes at the same time.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.