A
A
Alena2016-06-15 11:18:09
MySQL
Alena, 2016-06-15 11:18:09

How to install mariadb on top of mysql?

Good afternoon. There is a question about optimizing our web servers. Still vacillating between percona and mariadb.
The essence of the question is that in our infrastructure it is arranged in such a way that the application itself lies next to the database. Now a bunch of tomcat7 and muscle 5.5 and a night dump of the database. For optimization, we plan to set up master-slave replication. But to make it really good - also instead of a muscle - its fork.
How, without unnecessary manipulations - to make a muscle - Maria (or perkona)
Google does not understand my requests)

Answer the question

In order to leave comments, you need to log in

4 answer(s)
N
Nikolai Turnaviotov, 2016-06-15
@foxmuldercp

demolish the muscle, put Maria. in general, in centos 7 yum install muscle, I remember putting Maria already, or putting Maria, but #mysql starts Maria's client by alias

Q
qasdfwe, 2016-06-15
@qasdfwe

Docker

S
safenoob, 2016-06-15
@safenoob

Raise a new server, put everything you need from the very beginning. Transfer data, transfer everything to a new server, start everything from it and then turn off the old server.

L
landergate, 2016-06-27
@landergate

Regarding migration:
In a general situation, the following may be sufficient:

  1. Allocate non-working hours when it will be possible to carry out preventive maintenance.
  2. Make a backup copy of the database (both application and information_scheme)
  3. Stop MySQL
  4. Make a backup copy of the data files (/var/lib/mysql)
  5. Make a backup copy of configs from /etc/mysql
  6. Remove package: 'sudo apt-get remove mysql-server'
  7. Connect the MariaDB repository:
    https://downloads.mariadb.org/mariadb/repositories/
    Everything.
    What could go wrong:
    - Too much difference in configs could hypothetically cause the new server to have a problem reading existing data files, preventing the service from starting. In this case, the reason will most likely be written in /var/log/mysql.logor /var/log/mysql.err.
    I haven't experienced this before, but if it does, it's faster: uninstall MariaDB, then disable the repository (by removing the appropriate line/file from /etc/apt/sources.listor /etc/apt/sources.list.d/), then sudo apt-get update, then install the mysql-server package back. Before doing this, it's a good idea to roll back the /etc/mysql and /var/lib/mysql backups to their original locations in order to eliminate the consequences of changing the data files / configs by upgrading to MariaDB. Then analyze what went wrong and better prepare for the next migration attempt.
    Related materials with migration tips:
    https://mariadb.com/kb/en/mariadb/upgrading-from-m...
    https://mariadb.com/kb/en/mariadb/moving-to-mariadb/
    https://mariadb.com/blog/how-migrate-mysql-mariadb...
    https://www.digitalocean.com/community/tutorials/s...
    Often performance depends on application architecture, not to use a particular technology.
    For example, it's a good idea to learn indexes for heavy queries.
    Examples of how to choose columns for indexing:
    ruhighload.com/post/%D0%9A%D0%B0%D0%BA+%D0%BF%D1%8...
    ruhighload.com/index.php/2009/06 /09/%D0%BA%D0%B0%D...
    ruhighload.com/post/%D0%A0%D0%B0%D0%B1%D0%BE%D1%82...

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question