Christian Boltz wrote:
Hello,
Am Mittwoch, 10. Januar 2018, 11:54:03 CET schrieb Theo Chatzimichos:
It happened again twice, so it was definitely not a logrotate issue, but instead it was an upstream bug, possibly this [1]. So now I updated the hosts and mariadb was updated to a new patch version. Let's see if it crashes again now, if it does I'll file a ticket against our package.
It turned out that the mariadb update didn't change anything, and the cluster crashed at 19:31 UTC again - at least it was timely ;-)
Predictability is Good Thing(R) :-)
OTOH - who would have thought that optimizing all tables crashes the cluster? ;-)
Sounds like it ought to be reproducable. Unless we're optimizing in parallel? -- Per Jessen, Zürich (3.4°C) openSUSE mailing list admin -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org