[MXS-1806] Error in high concurrency when testing maxscale 2.2.4 Created: 2018-04-16 Updated: 2018-05-29 Resolved: 2018-05-29 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | 2.2.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Emma chan | Assignee: | Timofey Turenko |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
centos 6 |
||
| Sprint: | MXS-SPRINT-56, MXS-SPRINT-57, MXS-SPRINT-58, MXS-SPRINT-59 |
| Description |
|
I want to run testing against proxysql and maxscale with sysbench, when I test proxysql,everythin is ok. but when i test maxscale,
this is the sysbench command:
when i set --threads to less than 64, no errors reported. it seems like that when the concurrency is high, maxscale can't handle it. below attached my maxscale.cnf, i don't know if any mistake in the config file.
|
| Comments |
| Comment by markus makela [ 2018-04-16 ] |
|
Does the MaxScale log contain any error messages? |
| Comment by Emma chan [ 2018-04-17 ] |
|
no error in maxscale.log |
| Comment by Johan Wikman [ 2018-04-17 ] |
|
emma How many cores do you have in your MaxScale machine? Try changing threads=auto to e.g. threads=8. Does it make any difference? |
| Comment by Emma chan [ 2018-04-18 ] |
|
my MaxScale machine has 8 cores |
| Comment by Johan Wikman [ 2018-04-19 ] |
|
Thanks emma, then there's nothing special about that. We'll have to investigate. |
| Comment by Timofey Turenko [ 2018-04-19 ] |
|
I can't reproduce. Probably I use different HW and network. |
| Comment by Timofey Turenko [ 2018-05-29 ] |
|
can't reproduce |