Age | Commit message (Collapse) | Author | Files | Lines |
|
This reverts commit 8a696682b3fd0cb5f32ddaca8ede5db7b001a57f.
Change-Id: Ib1698643639436243768f4a8209c4d68314a97ca
|
|
xtrabackup issues have been fixed with the latest version of
percona-xtrabackup DEBs we added to linux.enea.com, so remove
MySQL WSREP SST provider patches and corresponding docs.
Closes-bug: ARMBAND-52
Change-Id: I743e9b6ed242cf15e3063d7dcf7e05d0cee198f2
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
Change-Id: Ic5cc1109df04a95a5e072ab3acb79eb89427a1e0
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
|
|
On some arm64 platforms xtrabackup is broken due to an outdated
MySQL/InnoDB code that it uses which is missing. To work around that
this patch allows choosing which WSREP SST provider to use. Aside of
already supported `xtrabackup-v2` and `mysqldump`, the `rsync` method
has been added as it is comparable to xtrabackup in terms of speed (or
is faster), has been validated to work on arm64 platforms where
xtrabackup is broken and it doesn't rely on db mechanisms to perform the
state transfer.
This patch is tied to a patch in fuel-web that introduces configuration
options for WSREP SST provider and in case nothing is specified, it
will choose `xtrabackup-v2`.
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com>
|