wsrep API defines a set of application callbacks and replication library calls necessary to implement synchronous writeset replication of transactional databases and similar applications. It aims to abstract and isolate replication implementation from application details. Although the main target of this interface is a certification-based multi-master replication, it is equally suitable for both asynchronous and synchronous master/slave replication.
Application callbacks provide management of transaction write sets:
* populating of write sets, in the sending side
* applying of write sets, in the receiving end
The applying of received writesets is done by high priority transaction(s).
There are also calls for providing "total order isolated" processing of certain SQL statements. This feature guarantees that each database server in the cluster process the SQL statement in the same order and uninterrupted. .e.g. all DDL statements need to be processed isolated, to maintain data consistency in the cluster.
Mailing list: http://
Project information
- Licence:
- GNU LGPL v2.1
View full history Series and milestones
trunk series is the current focus of development.
All bugs Latest bugs reported
-
Bug #1378890: wsrep_listener.c fails to compile
Reported -
Bug #1321219: Causal read timeout should be session variable
Reported -
Bug #1288498: Fix license terms: either GPL2.1 or LGPL
Reported -
Bug #1247402: pass write set flags to apply/commit callbacks
Reported -
Bug #1229821: Add open_data_buffer()/close_data_buffer() (was get_data_buffer()) methods
Reported
All blueprints Latest blueprints
-
wsrep state API
Registered -
Configuration Change Handler
Registered
