Incomplete
Details
Assignee
UnassignedUnassignedReporter
Egor LyutovEgor LyutovPriority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Egor Lyutov
Egor LyutovPriority
Smart Checklist
Smart Checklist
Smart Checklist
Created April 1, 2019 at 2:42 AM
Updated March 6, 2024 at 10:12 PM
Resolved December 10, 2023 at 8:42 AM
When it fails one node just doesn't finish it's transactions anymore. The log is full of "Too many connections" messages and that's it. The cluster hangs.
Log messages:
// 2019-03-31T00:40:07.882609Z 688242683 [Note] Aborted connection 688242683 to db: 'db_name' user: ‘user’ host: ‘***’ (Got an error reading communication packets) 2019-03-31T00:40:07.882724Z 688245257 [Note] Aborted connection 688245257 to db: 'db_name' user: ‘user’ host: ‘***’ (Got an error reading communication packets) 2019-03-31T00:40:07.882847Z 688243397 [Note] Aborted connection 688243397 to db: 'db_name' user: ’user’ host: ‘****’ (Got an error reading communication packets) 2019-03-31T00:40:07.882964Z 688242021 [Note] Aborted connection 688242021 to db: 'db_name' user: ‘user’ host: ‘***’ (Got an error reading communication packets) 2019-03-31T00:40:08.471147Z 0 [Warning] Too many connections 2019-03-31T00:40:08.474331Z 0 [Warning] Too many connections 2019-03-31T00:40:08.479334Z 0 [Warning] Too many connections 2019-03-31T00:40:08.484204Z 0 [Warning] Too many connections 2019-03-31T00:40:08.485755Z 0 [Warning] Too many connections 2019-03-31T00:40:08.487274Z 0 [Warning] Too many connections 2019-03-31T00:40:08.501518Z 0 [Warning] Too many connections 2019-03-31T00:40:08.517456Z 0 [Warning] Too many connections
This happens regardless of the load, sometimes at night when the load is minimal.