[MDEV-17465] in galera cluster, Create Sequence's INCREMENT option must be updated, because nextval() function is occuring a Duplicate entry Error Created: 2018-10-16 Updated: 2021-04-26 Resolved: 2019-05-13 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Sequences |
| Affects Version/s: | 10.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Seonghwan Kim | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | galera, sequences | ||
| Description |
|
Hi, in galera cluster, Create Sequence's INCREMNET option must be updated, because nextval() function is occuring a Duplicate entry Error. when using 2-node Galera Cluster, insert into tbs33 (b) values(111); sometime after, I thought Sequence function must be updated. See below description. [...at the time of creation...] Galera Cluster's node flexibility is not reflecting in recent version of MariaDB Sequecne engine. |
| Comments |
| Comment by Elena Stepanova [ 2018-10-16 ] |
|
monty, serg, jplindst, what do you think about this? The complaint seems reasonable from the normal-user-scenario point-of-view, but I suppose the change might cause weird unwanted consequences and side effects. |
| Comment by Jan Lindström (Inactive) [ 2019-05-13 ] |
|
Based on description sequence works as designed and documented. When a new Galera node joins a cluster it does either incremental or full state transfer. This means that this joiner will copy database state from one of the nodes i.e. donor meaning that database objects are not created. For sequence case if setting the initial value is important user can use alter sequence for it. |