| === chris14_ is now known as chris14 | ||
| keithzg | Hmmmm I find myself in a position where I need to serve one database from an older Ubuntu+Mariadb stack than most of ours, but I still want a read-only copy on the primary server and no chance that the other node will overwrite anything other than that one database on the primary . . . this doesn't actually seem to be a supported use-case? I feel like I must be missing something because periodically overwriting the read-only central node's copy with a | 02:29 |
|---|---|---|
| keithzg | dump seems to be my best option?? | 02:29 |
| keithzg | (Oh, the strange places I find myself in, trying to support software that all the engineers at work insist on using despite it last being updated in 2011 :P) | 02:31 |
| sarnold | use zfs on both, have the writer on a writable dataset, and periodically zfs send to the reader? | 02:32 |
| keithzg | I was definitely considering something hacky like that (though not ZFS, I've never gotten along well with ZFS), was really hoping I was missing something native to the database layer itself though | 02:34 |
| keithzg | Going a bit higher-level and just using rsync, seems to work fine after I flush the tables so that the reader doesn't presume nothing has changed, I'm excited to eventually find out why this is a terrible plan ;) | 03:26 |
| === cpaelzer_ is now known as cpaelzer | ||
| === ch0ps3y is now known as Guest7344 | ||
| === ShadowLabs2 is now known as ShadowLabs | ||
| === stgraber is now known as Guest491 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!