recaptime.dev
@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Diviner: Remove lines about mixing MyISAM and InnoDB tables
Summary:
Phorge stopped using MyISAM tables long ago.
See for example https://we.phorge.it/Q82 and https://we.phorge.it/T16083
Test Plan: Run `./bin/diviner generate`, read http://phorge.localhost/book/phorge/article/cluster_databases/
Reviewers: O1 Blessed Committers, valerio.bozzolan
Reviewed By: O1 Blessed Committers, valerio.bozzolan
Subscribers: avivey, tobiaswiese, valerio.bozzolan, Matthew, Cigaryno
Differential Revision: https://we.phorge.it/D26473
+4
-7
+4
-7
src/docs/user/cluster/cluster_databases.diviner
+4
-7
src/docs/user/cluster/cluster_databases.diviner
···
58
58
privilege, Phorge's status console can give you more information about
59
59
replica health and state.
60
60
61
-
**Copying Data to Replicas**: Phorge currently uses a mixture of MyISAM
62
-
and InnoDB tables, so it can be difficult to guarantee that a dump is wholly
63
-
consistent and suitable for loading into a replica because MySQL uses different
64
-
consistency mechanisms for the different storage engines.
61
+
**Copying Data to Replicas**: Phorge uses InnoDB tables if available.
62
+
Phorge still allows MyISAM for older database server software.
65
63
66
-
An approach you may want to consider to limit downtime but still produce a
67
-
consistent dump is to leave Phorge running but configured in read-only
68
-
mode while dumping:
64
+
An approach you may want to consider to limit downtime and produce a dump is
65
+
to leave Phorge running but configured in read-only mode while dumping:
69
66
70
67
- Stop all the daemons.
71
68
- Set `cluster.read-only` to `true` and deploy the new configuration. The