[MCOL-4279] ExeMgr spawns infinite number of threads Created: 2020-08-27 Updated: 2021-09-06 Resolved: 2021-02-22 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ExeMgr |
| Affects Version/s: | 1.5.3 |
| Fix Version/s: | 5.4.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Patrick Safarov | Assignee: | David Hall (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2021-2, 2021-3, 2021-4 |
| Description |
|
The threads seem to spawn for each job. |
| Comments |
| Comment by David Hall (Inactive) [ 2021-01-29 ] | ||
|
I ran some tests and couldn't reproduce in 5.5.1 | ||
| Comment by Patrick Safarov [ 2021-01-30 ] | ||
|
I run mariadb in docker from mariadb/columnstore image id 5a61255d059f.
If you need any additional information, I am glad to provide it | ||
| Comment by Todd Stoffel (Inactive) [ 2021-02-10 ] | ||
|
Where is this docker image coming from? Please use the official release here: | ||
| Comment by Patrick Safarov [ 2021-02-11 ] | ||
|
I am using the official image, with few basic settings | ||
| Comment by Patrick Safarov [ 2021-02-11 ] | ||
|
The image id specified above was the latest one at the moment of downloading official image from docker hub | ||
| Comment by Daniel Lee (Inactive) [ 2021-02-22 ] | ||
|
I just tried the latest image (97f7df0d1068) and did not see the reported issue. docker run -d -p 3306:3306 --name mcs_container mariadb/columnstore [root@f23ec9d9a05f columnstore]# cat exemgr.log | ||
| Comment by David Hall (Inactive) [ 2021-02-22 ] | ||
|
We've tried a number of configurations, with and without docker. We specifically pulled the image from https://hub.docker.com/r/mariadb/columnstore. In all cases we couldn't get the number of threads to compound. The original poster (OP) says "The threads seem to spawn for each job". Not being sure what OP meant by "job", we went with the assumption it could mean either "mysql session" or"query". After hundreds of connections and thousands of queries, we saw no explosion of threads. It is possible that OP is using an older version and the problem has been fixed in the version we tested. We suggest OP download the latest (should be 5.5.1 by now) and try to reproduce the symptom. |