Skip to content

Orchestrator 4.31 cannot discover MariaDB 12.3 #127

Closed

Description

@ultim-ate

This issue is due to 'read-only' boolean parameter in the MariaDB 12.3 instead of smallint in previous versions:
+------------------------+--------------------+
| @@Version | @@global.read_only |
+------------------------+--------------------+
| 12.3.2-MariaDB-ubu2404 | OFF |
+------------------------+--------------------+

Activity

  1. renecannao commented on Aug 28, 2026

    @renecannao

    Thank you for the report.

    We reproduced and fixed this: MariaDB 12.3 changed @@global.read_only from a smallint to a boolean, which broke the scan orchestrator performs during instance discovery.

    See PR #121 , thanks @ahmetsoguksu .
    The fix is already on our master branch: the discovery query now normalizes the value with CASE WHEN UPPER(CAST(@@global.read_only AS CHAR)) IN ('0','OFF') THEN 0 ELSE 1 END, which works across MySQL and all MariaDB versions. We also added MariaDB 12.3 to our functional CI matrix (alongside MariaDB 10.6/10.11, MySQL 5.7–9.x and PostgreSQL), and discovery of MariaDB 12.3 now passes.

    The fix will ship with the next release, which we expect to publish later today. Please upgrade to that release once available.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions