[Maria-discuss] Error writing to binary log file
Hello, I have several MariaDB 10.1.45 instances running in Linux containers with memory limits. This week I have enabled binary logging on all of them with the following parameters: log-bin = mysqld-bin binlog-format = mixed expire_logs_days = 1 After that I have been getting several errors like this in a few of them: [ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 11 "Resource temporarily unavailable") A few also show these other two errors mixed with the previous one: [ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 12 "Cannot allocate memory") [ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 0 "Internal error/check (Not system error)") It gets stuck on this state, reporting errors to every attempt of executing a query. A restart on the service seems to solve the problem, at least temporarily. Does anybody have a clue on why it gets stuck like that? If the container ran out of memory, should not mariadb crash? I could not find any information about this error and binary logs being related. Thanks in advance, Gustavo Vieira
On Thu, 28 May 2020 16:24:23 -0300 Gustavo Vieira <gustavo@digirati.com.br> wrote:
Hello,
I have several MariaDB 10.1.45 instances running in Linux containers with memory limits.
Sounds like your out of memory that happens to be showing up when you write to the binary log. Can you monitor the memory use over time?
This week I have enabled binary logging on all of them with the following parameters: log-bin = mysqld-bin binlog-format = mixed expire_logs_days = 1
After that I have been getting several errors like this in a few of them:
[ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 11 "Resource temporarily unavailable")
A few also show these other two errors mixed with the previous one:
[ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 12 "Cannot allocate memory") [ERROR] mysqld: Error writing file 'mysqld-bin' (errno: 0 "Internal error/check (Not system error)")
It gets stuck on this state, reporting errors to every attempt of executing a query. A restart on the service seems to solve the problem, at least temporarily.
Does anybody have a clue on why it gets stuck like that? If the container ran out of memory, should not mariadb crash?
I could not find any information about this error and binary logs being related.
Thanks in advance, Gustavo Vieira
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Thanks for the quick reply!
Sounds like your out of memory that happens to be showing up when you write to the binary log.
Can you monitor the memory use over time?
Those errors started after I enabled bin-log, should I expect a higher memory consumption after enabling it? Also, if a lack of memory is the problem, I do not understand why the errors continue when, later, there is free memory.
participants (2)
-
Daniel Black
-
Gustavo Vieira