[MCOL-4997] too many threads running in ExeMgr? Created: 2022-02-23  Updated: 2023-02-24

Status: Open
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: 6.1.1, 6.2.3
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Massimo Assignee: Unassigned
Resolution: Unresolved Votes: 4
Labels: None
Environment:

CentOS Linux release 7.8.2003


Attachments: File explodeExemgr.bash     File mcs1_columnstore_error_log.bash     File mcs1_debug_log.bash     File mcs1_mariadb_error_log.bash     File mcs2_columnstore_error_log.bash     File mcs2_mariadb_error_log.bash     File mcs3_columnstore_error_log.bash     File mcs3_mariadb_error_log.bash    
Issue Links:
Duplicate
duplicates MCOL-5384 Plugin code leaks network connections... Closed
Relates
relates to MCOL-5384 Plugin code leaks network connections... Closed

 Description   

Summary
Too many process running for ExeMgr , this is slowing the system down consuming resources. Until columnstore is restarted these threads dont close.

Expected
Once a query completes, threads of ExeMgr that are spawned are properly closed.

Actual
New threads keep appearing never closing. These appear to spawn when queries are waiting to be executed.

Reproduction

bash explodeExemgr.bash
bash explodeExemgr.bash 300

then watch the following

strace -p $(pidof ExeMgr)
cat /proc/$(pidof PrimProc)/status | grep -i threads
cat /proc/$(pidof ExeMgr)/status | grep -i threads
ps -efT | grep ExeMgr | wc -l



 Comments   
Comment by Roman [ 2022-03-25 ]

Plz describe what do you mean by stress tests in the context alexey.vorovich ?

Comment by Ricardo Galvan [ 2022-04-05 ]

hi team, what are the next steps here? We are getting a lot of pressure from the customer to give an update, so what can we share with them today?

Comment by alexey vorovich (Inactive) [ 2022-08-08 ]

massimo.disaro Please see the comment above. Without reproduction , there is not much we can do

Comment by Roman [ 2023-02-24 ]

massimo.disaro Presumably MCOL-5384 resolves this issue.

Generated at Thu Feb 08 02:54:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.