[MXS-4870] Maxscale dump in RoutingWorker::execute_concurrently Created: 2023-11-22 Updated: 2024-01-22 Resolved: 2024-01-22 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | 22.08.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Jiri Srba | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | crash | ||
| Environment: |
production |
||
| Description |
|
The maxscale process failed with the following backtrace. This is the performance issue. The one maxscale is capable up to 5k connections. Over the 5k connection, the response is quite slow .. and after few minutes the maxscale crash.
The current maxscale configuration
|
| Comments |
| Comment by Johan Wikman [ 2023-11-22 ] |
|
Signal 6 typically means that MaxScale was killed by the systemd watchdog. You could try to replace the domain names (db-1 etc) with their real IPs, as domain name lookup may take a while and have been known to cause problems. Also follow the instructions from the log 2023-11-21 11:57:17 notice : For a more detailed stacktrace, install GDB and add 'debug=gdb-stacktrace' under the [maxscale] section. as that will provide a more informative stack-trace. |
| Comment by markus makela [ 2023-12-04 ] |
|
You can also try to install MaxScale 23.08 which has a built-in functionality for dumping stacktraces of all threads. |
| Comment by Jiri Srba [ 2023-12-04 ] |
|
upgraded to maxscale 23.08 version, thanks |
| Comment by markus makela [ 2024-01-08 ] |
|
jiri.srba any updates? |
| Comment by markus makela [ 2024-01-22 ] |
|
I'll close this as Incomplete due to no feedback with the latest version. If this occurs with the latest version again, please report back and we'll reopen it. |