Skip to content

Conversation

@nastena1606
Copy link
Collaborator

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

…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
Copy link

Copilot AI left a 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_handler integration 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>
@it-percona it-percona temporarily deployed to K8SPXC-735-Doc-ProxySQL-scheduler - percona-mysql-operator-pxc PR #272 November 27, 2025 13:56 — with Render Destroyed
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

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.
Copy link
Contributor

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 ?

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.
Copy link
Contributor

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.

Comment on lines 24 to 25
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.
Copy link
Contributor

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?

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.

4 participants