Details
Description
CREATE SEQUENCE CHANGE_EVENTS_SID_SEQ START WITH 1577836800000000 INCREMENT BY 1;
ERROR 1235 (42000): This version of MariaDB doesn't yet support 'In Galera if you use CACHE you should set INCREMENT BY 0 to behave correctly in a cluster'
It also failed with other MariaDB releases using Galera starting. (Works without Galera enabled)
version = 10.6.16-11-MariaDB-enterprise-log
version = 10.5.22-16-MariaDB-enterprise-log
wsrep_provider_version = 26.4.14-1(ra480e94)
wsrep_provider_version = 26.4.16
wsrep_patch_version = wsrep_26.22
Workaround it by adding the NOCACHE option per example below:
CREATE SEQUENCE CHANGE_EVENTS_SID_SEQ START WITH 1577836800000000 INCREMENT BY 1 NOCACHE;
Query OK, 0 rows affected (1.417 sec)
Attachments
Issue Links
- is caused by
-
MDEV-30388 Assertion `!wsrep_has_changes(thd) || (thd->lex->sql_command == SQLCOM_CREATE_TABLE && !thd->is_current_stmt_binlog_format_row()) || thd->wsrep_cs().transaction().state() == wsrep::transaction::s_aborted' failed
-
- Closed
-
- relates to
-
-
- Closed
-
Activity
It didn't work as such. It had a bug MDEV-30388.
This bug was fixed in 10.6.15 by disallowing sequences with use CACHE and non-zero INCREMENT in galera.
It worked and still does.
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 224128
Server version: 10.6.12-7-MariaDB-enterprise MariaDB Enterprise Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> create schema blah;
Query OK, 1 row affected (0.022 sec)
MariaDB [(none)]> use blah
Database changed
MariaDB [blah]> CREATE SEQUENCE CHANGE_EVENTS_SID_SEQ START WITH 1577836800000000 INCREMENT BY 1;
Query OK, 0 rows affected (0.055 sec)
MariaDB [blah]> show global status like 'wsrep_provider_version';
-------------------------------------------+
| Variable_name | Value |
-------------------------------------------+
| wsrep_provider_version | 26.4.14-1(ra480e94) |
-------------------------------------------+
1 row in set (0.000 sec)
MariaDB [blah]> select version;
ERROR 1054 (42S22): Unknown column 'version' in 'field list'
MariaDB [blah]> select version();
------------------------------
| version() |
------------------------------
| 10.6.12-7-MariaDB-enterprise |
------------------------------
1 row in set (0.000 sec)
MariaDB [blah]>
Where is the bug here? The error says MariaDB doesn't yet support — which looks like a very intentional behavior to me.