Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.5.5
-
Production
Description
We have a mariadb 3-node Cluster (Galera) version 10.5.5. We are getting the following warnings in the database error log:
2021-03-30 11:15:42 375 [Warning] Aborted connection 375 to db: 'DB_NAME' user: 'USER_NAME' host: 'HOST_NAME' (Got an error writing communication packets)
At the same time at the application level, the user performing the insert operations gets the following errors:
2021-03-30 11:15:24.915 SEVERE [SFCScheduler_Worker-1]
Caused by: java.sql.SQLNonTransientConnectionException: (conn=375) unexpected end of stream, read 0 bytes from 4 (socket was closed by server)
... 5 more
Caused by: java.sql.SQLException: unexpected end of stream, read 0 bytes from 4 (socket was closed by server)
Query is: COMMIT
We have checked the following parameters at database level:
MariaDB [(none)]> SHOW VARIABLES LIKE "%version%";
---------------------------------------------------------------------------+
Variable_name | Value |
---------------------------------------------------------------------------+
in_predicate_conversion_threshold | 1000 |
innodb_version | 10.5.5 |
protocol_version | 10 |
slave_type_conversions | |
system_versioning_alter_history | ERROR |
system_versioning_asof | DEFAULT |
tls_version | TLSv1.1,TLSv1.2,TLSv1.3 |
version | 10.5.5-MariaDB |
version_comment | MariaDB Server |
version_compile_machine | x86_64 |
version_compile_os | Linux |
version_malloc_library | system |
version_ssl_library | OpenSSL 1.0.2k-fips 26 Jan 2017 |
wsrep_patch_version | wsrep_26.22 |
---------------------------------------------------------------------------+
15 rows in set (0.001 sec)
MariaDB [(none)]>
MariaDB [(none)]> show global status like '%abort%';
-------------------------------+
Variable_name | Value |
-------------------------------+
Aborted_clients | 126 |
Aborted_connects | 34 |
Aborted_connects_preauth | 7 |
wsrep_local_bf_aborts | 1295 |
-------------------------------+
4 rows in set (0.001 sec)
MariaDB [(none)]> show global variables like 'wait_timeout';
--------------------+
Variable_name | Value |
--------------------+
wait_timeout | 28800 |
--------------------+
1 row in set (0.001 sec)
MariaDB [(none)]> show global variables like 'interactive_timeout';
--------------------------+
Variable_name | Value |
--------------------------+
interactive_timeout | 28800 |
--------------------------+
1 row in set (0.001 sec)
MariaDB [(none)]> show global variables like 'max_allowed_packet';
------------------------------+
Variable_name | Value |
------------------------------+
max_allowed_packet | 1073741824 |
------------------------------+
1 row in set (0.001 sec)
MariaDB [(none)]> show global variables like 'max_connections';
----------------------+
Variable_name | Value |
----------------------+
max_connections | 151 |
----------------------+
1 row in set (0.001 sec)
MariaDB [(none)]> show global variables like 'innodb_log_%';
--------------------------------------+
Variable_name | Value |
--------------------------------------+
innodb_log_buffer_size | 16777216 |
innodb_log_checksums | ON |
innodb_log_compressed_pages | ON |
innodb_log_file_size | 100663296 |
innodb_log_files_in_group | 1 |
innodb_log_group_home_dir | ./ |
innodb_log_optimize_ddl | OFF |
innodb_log_write_ahead_size | 8192 |
--------------------------------------+
8 rows in set (0.001 sec)
MariaDB [(none)]>
But we are not able to see the root cause of those "writing communication packets" issues and the timeouts at the application level. ¿Could you please give us some support in order to solve those issues? Thank you.
Best regards,
Diana.