maria-discuss team mailing list archive
Mailing list archive
Re: MariaDB 10.1: binlog stop updating
On 21/02/2019 14:19, andrei.elkin@xxxxxxxxxx wrote:
> To the issue itself
> > 2019-02-20 15:24:12 140618945124096 [ERROR] Slave SQL: Could not execute
> > Write_rows_v1 event on table xxx.yyyy; Error writing file
> > '/tmp/MLxClNzW' (Errcode: 28 "No space left on device"), Error_code: 3;
> the error was caused by ROW format event and therefore does not do with
yeah that's what i feared.
>> I was looking at using a separate tmp space for the slave needs
>> using slave_load_tmpdir
> the parameter above but indeed check out @@global.tmpdir location and
> size available.
Yes as i said initially, the binlog corruption issues are related to
saturations in tmpdir location.
The initial issue is this strange huge increase in tmpdir space with
mariadb 10.1 were previously 4Gb was largely enough and now even 5 times
this (20Gb) isn't anymore ...
> Perhaps the
someone ate a few words here ;)
Thanks for your insight anyway!