-
Notifications
You must be signed in to change notification settings - Fork 25
K8SPXC-735 Documented new ProxySQL scheduler options and behavior #272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…operator and configuration files. Added details on enabling the scheduler, its impact on load balancing, and configuration examples for better clarity.
modified: docs/operator.md
modified: docs/proxysql-conf.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds comprehensive documentation for the new ProxySQL scheduler feature introduced in Operator version 1.19.0. The scheduler provides better read/write splitting and load balancing across Percona XtraDB Cluster nodes.
Key Changes:
- Documents the
pxc_scheduler_handlerintegration and its benefits for load balancing - Adds configuration examples and behavioral details for the ProxySQL scheduler
- Includes new Custom Resource options for scheduler configuration
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/proxysql-conf.md | Added ProxySQL scheduler section with enablement instructions, behavior documentation, and general content improvements for clarity |
| docs/operator.md | Added documentation for seven new scheduler-related Custom Resource options (enabled, writerIsAlsoReader, checkTimeoutMilliseconds, etc.) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
docs/proxysql-conf.md
Outdated
|
|
||
| You can enable ProxySQL only when you create a cluster. For a running cluster you can enable only HAProxy. Also note, if you have already enabled HAProxy, the switch from it to ProxySQL is not | ||
| possible. | ||
| You can enable ProxySQL only during cluster creation. For existing clusters, you can enable only HAProxy. If HAProxy is already enabled, you cannot switch to ProxySQL later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think we can remove this warning now, right @gkech ?
docs/proxysql-conf.md
Outdated
| You may want to configure the ProxySQL service as a [headless Service :octicons-link-external-16:](https://kubernetes.io/docs/concepts/services-networking/service/#headless-services). For example, if you have applications that need direct DNS access to individual ProxySQL pods, such as when running in a multi-tenant setup or when handling advanced networking scenarios. | ||
|
|
||
| This annotation works only at service creation time and can't be added later. | ||
| To enable a headless ProxySQL service, add the `percona.com/headless-service: true` [annotation](annotations.md) in the Custom Resource metadata section of the `deploy/cr.yaml` file. Note that this annotation takes effect only at service creation time, so you need to set it when first creating the cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is wrong. this annotation needs to be added into either proxysql.expose.annotations, haproxy.exposePrimary.annotations or haproxy.exposeReplicas.annotations.
deeb1df to
84ccf9e
Compare
docs/haproxy-conf.md
Outdated
| Switching from ProxySQL to HAProxy will cause Percona XtraDB Cluster Pods | ||
| restart. Switching from HAProxy to ProxySQL is not possible, and if you need | ||
| ProxySQL, this should be configured at cluster creation time. | ||
| restart. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gkech is this true? i mean does switching proxies require PXC pods to restart?
Added details on enabling the scheduler, its impact on load balancing, and configuration examples for better clarity.
modified: docs/operator.md
modified: docs/proxysql-conf.md