20a9cb73fe
This change adds new options for controlling the SST using the mariabackup method, which in many cases will allow much more effective management of the free space used during the SST process. Two new options have been added, which can be used in the configuration file by placing them in the [sst] section: 1) The 'sstdir' option sets the path to the temporary directory where the received files will be placed during the state transfer process in SST using mariabackup. Before this change, files were always written to a special directory <datadir>/.sst, which created a problem if the storage where datadir resides was close to full. Now, however, it is possible to specify an arbitrary directory where the system will place the files received during SST. Attention! The directory specified with sstdir will be deleted during the SST process – therefore, it cannot be the datadir itself or any important user directory containing valuable files! It must be a working temporary directory that will be automatically removed by the system at the end of SST. The user can also set the special value sstdir='mktemp'. In this case, the system will automatically create a working directory for SST using the mktemp utility (possibly using the tmpdir directory if it is specified in the configuration file). This directory will be deleted after the SST is completed. 2) The 'cleaning' option allows controlling the timing of the deletion of the current system state when SST is required. Currently, as well as by default after this change, the current state is deleted in parallel with the transfer of new data during SST. This is optimal in terms of performance but may cause problems if the storage where datadir resides has little free space and the same storage is used for receiving files – because the old files are not deleted immediately, but only after some time. If the user is interested in deleting the current state before the start of SST, which allows freeing up space on the datadir storage, they can now set the option cleaning='before', and the current state will be deleted before SST starts. This may be slower in terms of performance but frees up space, which can be critical in some user scenarios. On the other hand, the user can specify cleaning='after' – in this case, the current state will be deleted only after the successful completion of data transfer during SST. This reduces performance and requires more free space but guarantees that the current state will not be deleted on the node before the successful completion of data transfer – which can critically increase reliability in user scenarios where loss of state on nodes due to a chain of failures during SST transfer creates a risk of cluster degradation. If the user specifies cleaning='parallel' or does not set any value for this option, the system will operate as before – deleting the current state in parallel with receiving new data. This maximizes performance but requires large amounts of free space in the location specified by sstdir and may result in the loss of node state if data transfer during SST fails. |
||
|---|---|---|
| .github | ||
| BUILD | ||
| client | ||
| cmake | ||
| dbug | ||
| debian | ||
| Docs | ||
| extra | ||
| include | ||
| libmariadb@77bdf5a572 | ||
| libmysqld | ||
| libservices | ||
| man | ||
| mysql-test | ||
| mysys | ||
| mysys_ssl | ||
| plugin | ||
| randgen/conf | ||
| scripts | ||
| sql | ||
| sql-bench | ||
| sql-common | ||
| storage | ||
| strings | ||
| support-files | ||
| tests | ||
| tpool | ||
| unittest | ||
| vio | ||
| win | ||
| wsrep-lib@14ce8cab76 | ||
| zlib | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| appveyor.yml | ||
| BUILD-CMAKE | ||
| CMakeLists.txt | ||
| config.h.cmake | ||
| configure.cmake | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| CREDITS | ||
| INSTALL-SOURCE | ||
| INSTALL-WIN-SOURCE | ||
| KNOWN_BUGS.txt | ||
| README.md | ||
| THIRDPARTY | ||
| VERSION | ||
Code status:
ci.appveyor.com
MariaDB: The innovative open source database
MariaDB was designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.
MariaDB is brought to you by the MariaDB Foundation and the MariaDB Corporation. Please read the CREDITS file for details about the MariaDB Foundation, and who is developing MariaDB.
MariaDB is developed by many of the original developers of MySQL who now work for the MariaDB Corporation, the MariaDB Foundation and by many people in the community.
MySQL, which is the base of MariaDB, is a product and trademark of Oracle Corporation, Inc. For a list of developers and other contributors, see the Credits appendix. You can also run 'SHOW authors' to get a list of active contributors.
A description of the MariaDB project and a manual can be found at:
https://mariadb.com/kb/en/mariadb-vs-mysql-features/
https://mariadb.com/kb/en/mariadb-versus-mysql-compatibility/
https://mariadb.com/kb/en/new-and-old-releases/
Getting the code, building it and testing it
Refer to the following guide: https://mariadb.org/get-involved/getting-started-for-developers/get-code-build-test/ which outlines how to build the source code correctly and run the MariaDB testing framework, as well as which branch to target for your contributions.
Help
More help is available from the Maria Discuss mailing list https://lists.mariadb.org/postorius/lists/discuss.lists.mariadb.org/ and MariaDB's Zulip instance, https://mariadb.zulipchat.com/
Licensing
MariaDB is specifically available only under version 2 of the GNU General Public License (GPLv2). (I.e. Without the "any later version" clause.) This is inherited from MySQL. Please see the README file in the MySQL distribution for more information.
License information can be found in the COPYING file. Third party license information can be found in the THIRDPARTY file.
Bug Reports
Bug and/or error reports regarding MariaDB should be submitted at: https://jira.mariadb.org
For reporting security vulnerabilities see: https://mariadb.org/about/security-policy/
The code for MariaDB, including all revision history, can be found at: https://github.com/MariaDB/server