All pages
Powered by GitBook
1 of 1

Loading...

MariaDB Galera Cluster 10.0.27 Changelog

The most recent MariaDB Galera Cluster 10.0 release is:MariaDB Galera Cluster 10.0.38 Download Now

DownloadRelease NotesChangelogOverview of MariaDB Galera Cluster

Release date: 29 Aug 2016

For the highlights of this release, see the release notes. For changes made in MariaDB, see the MariaDB 10.0.27 Changelog.

The revision number links will take you to the revision's page on Github. On Github you can view more details of the revision and view diffs of the code modified in that revision.

  • Revision #16702ec 2016-08-25 21:19:25 -0400

    • Record wsrep.variables test result (with non-debug galera library).

  • 2016-08-24 19:41:11 -0400 - Merge branch '5.5-galera' into 10.0-galera

  • 2016-07-19 20:44:02 +0000

    • : wsrep_client_thread was not set in threadpool.

  • 2016-08-10 14:48:44 -0400

    • MW-292: Fix test case

  • 2016-07-15 01:13:32 -0700

    • Galera MTR Tests: Test case for MW-292 : NOW() returns stale timestamp after transaction replay

  • 2016-07-14 14:29:59 +0200

    • MW-292 Reset timestamp after transaction replay

  • 2016-08-10 10:34:54 -0400 - Merge tag 'mariadb-5.5.51' into 5.5-galera

  • 2016-08-03 22:15:57 -0400

    • : Galera SST using rsync does not filter out lost+found

  • 2016-08-24 19:30:32 -0400 - Merge branch '10.0' into 10.0-galera

  • 2016-08-24 17:13:20 -0400

    • Fixes/improvements in galera test suite

  • 2016-08-24 15:32:48 -0400

    • : Create role statement replicated inconsistently in Galera Cluster

  • 2016-08-21 20:13:51 -0400

    • Update WSREP_PATCH_REVNO.

  • 2016-08-21 20:09:05 -0400

    • Fixes for failing tests (post-merge).

  • 2016-06-29 16:50:53 -0400

    • : cannot add new node to the cluser: Binlog..

  • 2016-06-08 15:19:01 +0300

    • Refs: MW-279 - fixes in innodb to skip wsrep processing (like kill victim) when running in native mysql mode

      • similar fixes in mysql server side

      • forcing tc_log_dummy in native mysql mode when no binlog used. wsrep hton messes up handler counter and used to lead in using tc_log_mmap instead. Bad news is that tc_log_mmap does not seem to work at all

  • 2016-08-12 10:57:58 +0200

    • refs codership/mysql-wsrep#267 Fix Galera crash at startup when compiled with gcc 6

  • 2016-08-09 12:34:03 +0300

    • Bump WSREP_PATCH_VERSION to 16

  • 2016-08-04 00:33:12 -0700

    • Galera MTR Tests: fortify galera_bf_abort_flush_for_export against sporadic failures.

  • 2016-08-03 02:52:39 -0700

    • Galera MTR Tests: Attempt to fortify galera_kill_ddl.test against sporadic failures

  • 2016-07-22 04:16:09 -0700

    • Galera MTR Tests: increase timeouts and adjust some sporadically-failing tests so that the Galera suites can be run with --parallel=4

  • 2016-07-13 03:19:20 -0700

    • Galera MTR Tests: Test case for galera#414 - crash on shutdown with gcs.max_packet_size=2

  • 2016-06-09 09:21:43 +0200

    • GCF-837 Fix crash when loading wrong provider version

  • 2016-06-13 17:49:42 +0200

    • GCF-837 Check wsrep interface version before loading provider

  • 2016-06-20 14:35:22 +0200

    • MW-285 MTR test case for broken foreign key constraints

  • 2016-06-02 16:44:54 +0530

    • PXC#592: Tried closing fk-reference-table that was never opened.

  • 2016-06-14 17:18:21 +0200

    • MW-286 Avoid spurious deadlock errors when wsrep_on is disabled

  • 2016-06-13 06:17:33 -0700

    • Galera MTR Tests: Run galera_pc_weight on freshly started servers in order to prevent interaction with other tests

  • 2016-06-07 10:46:14 +0300

    • refs: MW-279 - At startup time global wsrep_on is set too late and some wsrep paths may be executed because of this. e.g. replication slave restart could happen before wsrep_on state is defined.

      • This fix checks both global wsrep_on and wsrep_provider values to determine if wsrep processing should happen

      • Fix affects all instances where WSREP_ON macro is used

  • 2016-06-03 04:26:17 -0700

    • Galera MTR Tests: force galera_3nodes.galera_pc_bootstrap.test to run on a fresh cluster in order to avoid interaction with galera_3nodes.galera_innobackupex_backup.test

  • 2016-06-02 23:56:16 -0700

    • Galera MTR Tests: fortify galera_parallel_simple.test against sporadic failures

  • 2016-06-02 23:39:12 -0700

    • Galera MTR Tests: Fortify galera_restart_nochanges.test against sporadic failures due to node not being ready immediately after restart

  • 2016-05-18 11:07:58 +0200

    • MW-175 Fix definitively lost memory in wsrep_get_params

  • 2016-05-17 22:23:51 -0700

    • Galera MTR Tests: stability fixes

  • 2016-05-01 23:29:55 -0700

    • Galera MTR Tests: Adjust tests for xtrabackup 2.4.2

  • 2016-08-15 11:29:48 -0400

    • Fix galera/MW-44 test post-merge.

  • 2016-04-14 01:25:54 -0700

    • Galera MTR Tests: Adjust galera_log_output_csv.test to account for the fix for MW-44

  • 2016-04-14 01:03:37 -0700

    • Galera MTR Tests: A test for MW-44 - Disable general log for applier threads

  • 2016-04-05 14:08:39 +0300

    • MW-44 Disable general log for applier threads

  • 2016-08-15 11:14:57 -0400

    • Fix galera/ test post-merge.

  • 2016-04-04 07:09:32 -0700

    • Galera MTR Tests: Add test for , codership/galera#382 - InnoDB: Failing assertion: xid_seqno > trx_sys_cur_xid_seqno in trx0sys.cc line 356

  • 2016-04-04 05:32:50 -0700

    • Galera MTR Test: Fix for MW-258.test - do not use SHOW PROCESSLIST

  • 2016-04-04 05:14:13 -0700

    • Galera MTR Tests: Fixed tests to account for ,

  • 2016-04-02 22:37:22 -0300

    • MW-259 - moved wsrep desync/resync calls from wsrep_desync_update() to wsrep_desync_check() method which does not hold the lock and is arguably a more fitting place to change provider state - before changing the actual variable value.

  • 2016-08-12 14:03:24 -0400

    • Fix galera_ist_recv_bind.test.

  • 2016-04-02 21:51:26 -0300

    • MW-258 - RSU DDL should not rely on the global wsrep_desync variable value and should always try to desync on its own.

  • 2016-03-15 03:38:31 -0700

    • Refs codership/galera#105 An MTR test for ist.recv_bind

  • 2016-08-12 13:42:12 -0400

    • Fix galera_transaction_replay.test.

  • 2016-03-08 18:10:21 +0200

    • Refs MW-255

      • popping PS reprepare observer before BF aborted PS replaying begins dangling observer will cause failure in open_table() ater on

      • test case for this anomaly

  • 2016-03-07 23:34:03 +0200

    • Refs MW-252 - changed the condition when to do implicit desync as part of FTWRL to cover only case when node is PC and synced. Donor node has alreaydy desycned and other states mean that node is not in cluster, so desync is not even possible.

  • 2016-03-04 14:20:58 +0200

    • Bump WSREP_PATCH_VERSION to 14

  • 2016-08-12 12:56:41 -0400

    • Update galera version-dependent tests.

  • 2016-08-11 22:28:57 -0400

    • Refs: MW-252 Test fix post-merge

  • 2016-03-01 08:32:06 -0800

    • Refs: MW-252 MTR tests for FTWRL and desync

  • 2016-03-01 10:56:21 +0200

    • Refs: MW-252 - if wsrep_on==OFF, unlock tables would resume provider even though it was not passed in FTWRL processing. This is fixed in this patch.

  • 2016-02-29 22:54:58 +0200

    • Refs MW-252 - reverted from tracking donor servicing thread. With xtrabackup SST, xtrabackup thread will call FTWRL and node is desynced upfront - Skipping desync in FTWRL if node is operating as donor

  • 2016-02-29 16:36:17 +0200

    • Refs MW-252 - Calling FTWRL two times in a row caused desync error, this is fixed by making sub-sequent FTWRL calls bail out before wsrep operations

  • 2016-02-29 15:24:06 +0200

    • Refs MW-252 - enveloped FTWRL processing with wsrep desync/resync calls. This way FTWRL processing node will not cause flow control to kick in

      • donor servicing thread is unfortunate exception, we must let him to pause provider as part of FTWRL phase, but not desync/resync as this is done as part of donor control on higher level

  • 2016-02-19 13:08:22 +0200

    • Refs: MW-248 - some more code cleanup

  • 2016-02-19 13:02:59 +0200

    • refs: MW-248 - removed the off topic mtr test

  • 2016-02-19 11:48:09 +0200

    • Refs: MW-248 - fixed the test case and extended with autoinc modification is master side

  • 2016-02-18 14:34:53 +0200

    • Refs: MW-248 - test cases from PXC for reproducing the issue - initial fix

  • 2016-08-10 12:30:57 -0400

    • Cleanup: Remove dead code

  • 2016-01-11 22:43:27 +0200

    • refs codership/mysql-wsrep#239 Synced xtrabackup SST scripts from PXC source tree as of PXC 5.6.27-25.13

      • PXC#480: xtrabackup-v2 SST fails with multiple log_bin directives in my.cn

      • PXC#460: wsrep_sst_auth don't work in Percona-XtraDB-Cluster-56-5.6.25-25.

  • 2016-07-19 20:44:02 +0000

    • : wsrep_client_thread was not set in threadpool.

  • 2016-07-25 21:52:02 -0400

    • MW-292: Fix test case

  • 2016-07-15 01:13:32 -0700

    • Galera MTR Tests: Test case for MW-292 : NOW() returns stale timestamp after transaction replay

  • 2016-07-14 14:29:59 +0200

    • MW-292 Reset timestamp after transaction replay

  • 2016-07-25 11:51:21 -0400

    • MW-267 Enforce wsrep_max_ws_size limit in wsrep provider

  • 2016-05-06 16:07:53 +0200

    • MW-267 Enforce wsrep_max_ws_size limit in wsrep provider

  • 2016-05-05 13:20:32 +0200

    • MW-269 Fix outstanding issues with wsrep_max_ws_rows

  • 2016-07-20 18:12:17 -0400

    • MW-265 Add support for wsrep_max_ws_rows

  • 2016-05-03 16:22:01 +0200

    • MW-265 Add support for wsrep_max_ws_rows

PXC-416: Fix SST related issues.

  • PXC-389: Merge remote-tracking branch 'wsrep/5.6' into 5.6-wsrep-pxc389

  • Bug #1431101: SST does not clobber backup-my.cnf

  • Revision #b506d95
    Revision #d40d3f4
    MDEV-10314
    Revision #abfbe80
    Revision #dfadb36
    Revision #9a809fe
    Revision #38a0def
    Revision #44e3046
    MDEV-10487
    Revision #c309e99
    Revision #8b09db8
    Revision #1b7c5de
    MDEV-10566
    Revision #f381ad5
    Revision #3f481e5
    Revision #cced23c
    MDEV-9423
    Revision #415823a
    Revision #fec296c
    Revision #2e56c7f
    Revision #f01a16b
    Revision #30c6ac3
    Revision #0656453
    Revision #85b9718
    Revision #ea3ff73
    Revision #bf19492
    Revision #dfa9012
    Revision #c9ac48f
    Revision #88a1592
    Revision #a12fa57
    Revision #5996c7b
    Revision #0e83726
    Revision #5609020
    Revision #1cb01fe
    Revision #92162e6
    Revision #137af55
    Revision #db837fd
    Revision #81174c9
    Revision #182787f
    Revision #675bcf3
    Revision #f49500a
    Revision #3f22e74
    GAL-382
    Revision #9b42f09
    GAL-382
    Revision #fce9217
    Revision #dda1144
    GAL-391
    GAL-374
    Revision #d45b582
    Revision #4582a4b
    Revision #90d92d2
    Revision #a00f4b2
    Revision #b758e92
    Revision #4e4ad17
    Revision #d246630
    Revision #f3444c4
    Revision #8b998a4
    Revision #65cf1d3
    Revision #fe6ebb6
    Revision #a03c45f
    Revision #8ec50eb
    Revision #b159b66
    Revision #4290117
    Revision #da9650a
    Revision #ae0fec9
    Revision #5edf55b
    Revision #df96eb5
    Revision #a53ac77
    Revision #58386ca
    Revision #9f211d4
    MDEV-10314
    Revision #963673e
    Revision #e572878
    Revision #7431368
    Revision #cbc8a84
    Revision #74f80b3
    Revision #5197fcf
    Revision #e373f60
    Revision #3db92ee

    Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

    MariaDB may already be included in your favorite OS distribution. More information can be found on the page.

    Distributions which Include MariaDB

    This page is licensed: CC BY-SA / Gnu FDL