1

Topic: How to struggle with Aborted connection

I welcome, colleagues. A configuration such: Galera-Cluster Percona Xtradb 5.7 () + arbitrator ()
In broad gulls great variety here such messages
[spoiler] 2017-09-19T14:32:13.814590+03:00 3102148 [Note] Aborted connection 3102148 to db: ' DATABASE ' user: ' DB_USER ' host: ' xxx.xxx.xxx.xxx ' (Got an error reading communication packets)
2017-09-19T14:35:21.002922+03:00 3105112 [Note] Aborted connection 3105112 to db: ' DATABASE ' user: ' DB_USER ' host: ' xxx.xxx.xxx.xxx ' (Got an error reading communication packets)
2017-09-19T14:35:58.764416+03:00 3105652 [Note] Aborted connection 3105652 to db: ' DATABASE ' user: ' DB_USER ' host: ' xxx.xxx.xxx.xxx ' (Got an error reading communication packets)
2017-09-19T14:37:40.775292+03:00 3107134 [Note] Aborted connection 3107134 to db: ' DATABASE ' user: ' DB_USER ' host: ' xxx.xxx.xxx.xxx ' (Got an error reading communication packets)
2017-09-19T14:39:31.006404+03:00 3108806 [Note] Aborted connection 3108806 to db: ' DATABASE ' user: ' DB_USER ' host: ' xxx.xxx.xxx.xxx ' (Got an error reading communication packets)
2017-09-19T14:43:32.962027+03:00 3112574 [Note] Aborted connection 3112574 to db: ' DATABASE ' user: ' DB_USER ' host: ' xxx.xxx.xxx.xxx ' (Got an error reading communication packets) [/spoiler]
Thus all works, requests are executed regularly, errors from application are not present, the network between application and mysql functions lost-free packets.
But it would be desirable to understand whence such messages and as from them