Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4.18
-
None
-
None
-
None
Description
Hello Team,
Recently, we faced weird issue with the database which is running on MariaDB 10.4.18. The cluster has been setup with three node semi-sync replicas. All the instances had to be rebuild after applying OS patches where it was completed for two instance and primary was changed to the patch applied instance. When the last instance was rebuilt and syncing, the primary went down after connections started to throw exceptions for Out of memory.
When we dig through the issue, metrics was showing the replication user which was consuming more resources before the database crashed. Never went through this scenario where the primary results in crash while he secondary is syncing. Error log didn't have any information for 2 minutes during the crash at 2022-05-04 0:25:14
2022-05-04 0:14:14 6920340 [Warning] Aborted connection 6920340 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Out of memory.) |
2022-05-04 0:14:14 6920341 [Warning] Aborted connection 6920341 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Out of memory.) |
......
|
2022-05-04 0:25:14 0 [Warning] Aborted connection 0 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (Too many connections) |
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
|
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@2022-05-04 0:27:07 0 [Note] InnoDB: Using Linux native AIO |
2022-05-04 0:27:07 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins |