The Ultimate Guide to High Availability with MariaDB

Transient Application Error 'Got error 6 "No such device or address" during COMMIT '

You are viewing an old version of this question. View the current version here.

Our customer hit the following messages from their application once:

2024-11-20 05:00:36,453 ERROR [...] (default task-..) ...: : java.sql.SQLTransientConnectionException: (conn=330042) Got error 6 "No such device or address" during COMMIT 2024-11-20 05:00:36,026 ERROR [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (QuartzScheduler_EPRSScheduler-uapp11731988979352_ClusterManager) Couldn't rollback jdbc connection. (conn=253330) Communications link failure with primary host .... WSREP has not yet prepared node for application use: java.sql.SQLInvalidAuthorizationSpecException: (conn=253330) Communications link failure with primary host .... WSREP has not yet prepared node for application use

It is the first time the customer see this error and was not reproduced. The database consists of 2 active-active MariaDB 10.6.19 running on RHEL8.10, plus a Witness node also running on RHEL8.10 and a matching version Galera-4.

What could be the cause of the issue and what ?

Thanks and best regards,

Lawrence

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.