MySQL topology
MySQL runs on both nodes of the databases cluster:cluster-n03– treated operationally as the primary MySQL node.cluster-n04– treated operationally as the backup / replica MySQL node.
MySQL on cluster-n03
- Version:
mysql Ver 14.14 Distrib 5.7.33, for Linux (x86_64) - Service:
mysql.service(enabled, active) - Unit file:
/lib/systemd/system/mysql.service - Data / config:
- Uses the standard Debian/Ubuntu layout.
- Exact
datadirand replication settings require MySQL access.
- Access for the
yazanuser without a password is not permitted (ERROR 1045), so DBAs should use appropriate MySQL users/credentials. - Operationally, this node is considered the main write node for MySQL workloads.
MySQL on cluster-n04
- Version:
mysql Ver 14.14 Distrib 5.7.36, for Linux (x86_64) - Service:
mysql.service(enabled, active) - Unit file:
/lib/systemd/system/mysql.service
- Similar to
cluster-n03, we cannot read replication status without DB credentials. - Treated as the backup / replica node in case of issues with
cluster-n03.
Operational hints
-
To confirm roles and replication, DBAs should run:
- Application endpoints and failover logic for MySQL should be documented in the relevant application or infrastructure modules (load balancers, DNS, etc.).
Cron jobs & backups
cluster-n03
- No custom root crontab configured for MySQL or other database tasks.
- Only standard system cron jobs under
/etc/cron.*(e.g.logrotate,mdadm,fstrim, etc.).
cluster-n04
-
Root crontab includes a MySQL backup job:
- Runs at 03:05, 09:05, 15:05, and 21:05 every day.
- Executes
/root/mysql.backup.shas root (exact backup behavior is defined in that script).
cluster-n04 otherwise contain only standard OS maintenance jobs.
