Will beat MyISAM in sync?

0 like 0 dislike
4 views
Now synching the remote database with the server stopping the muscle, and run rsync. But base grow and with them grows and the downtime.
The question is how likely is it to get a broken table, if not to stop the muscle on the synchronization period? And if you do LOCK TABLES? And then another drive check. Of activity base on 99% SELECT.

PS. I know about the dumps and about the replication and actively use them, but in this case it's unreasonably difficult.
by | 4 views

4 Answers

0 like 0 dislike
FLUSH TABLES WITH READ LOCK;
Only this design globally blocks all write operations to files on the server. SELECT s work.
\r
Not really understand the background to this decision. Why not use replication or a simple dump?
by
0 like 0 dislike
Under sync you mean copy — because now you have it is only in one direction — from the remote server to your.
\r
You can use rsync instead of mysqldump then gzip, scp to remote server, and mysql < dump.sql on-premises — will be the same, but the remote server to stand almost will not be (will only lag on the execution time of the dump).
by
0 like 0 dislike
But why such a perversion with rsync? Than not came up replication?
\r
In any case, you can use mysqlhotcopy to copy the table files when running the server, and these copies to send to the slave using rsync.
by
0 like 0 dislike
There is another option — to use LVM and snapshots. Idle will not be true at the time of raising snapshot disk speed will fall.
by

Related questions

0 like 0 dislike
3 answers
asked Jun 1, 2019 by akimdi
0 like 0 dislike
4 answers
asked Jun 2, 2019 by dmitrydeco
0 like 0 dislike
1 answer
0 like 0 dislike
2 answers
asked Jun 3, 2019 by fokin_nikolay1989
0 like 0 dislike
1 answer
asked Jun 12, 2019 by Dannerty
110,608 questions
257,186 answers
0 comments
28,804 users