[MCOL-1702] Joblist thread pool leaks if mariadb client connection drops its connection early. Created: 2018-09-06  Updated: 2020-08-25  Resolved: 2019-01-24

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr, MDB Plugin
Affects Version/s: 1.1.5
Fix Version/s: 1.1.7, 1.2.3

Type: Bug Priority: Minor
Reporter: Roman Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Relates
relates to MCOL-2009 Fix jobstep abort Closed
Sprint: 2019-01

 Description   

Joblist thread pool doesn't release threads occupied by JobList steps if mariadb client breaks its connection before the JobList step finishes.
To reproduce one should follow these steps:

  • Joblist thread pool debugging must be enabled in Columnstore.xml first
    <JobList>
    <ThreadPoolDebug>Y</ThreadPoolDebug>
  • run select * from tpch1c.lineitem and hit ctrl+c before the query returns the result set.
  • then number of Active threads in
    /var/log/mariadb/columnstore/trace/ThreadPool_ExeMgrJobList.log must be >=
    10 and it won't decrease.

 Comments   
Comment by Patrick LeBlanc (Inactive) [ 2018-12-10 ]

MCOL-2009 may be a requirement for this. A broken connection must abort the associated query.

Comment by Andrew Hutchings (Inactive) [ 2019-01-11 ]

I think this is a duplicate of MCOL-2009. Any objection to marking it as such?

Comment by Patrick LeBlanc (Inactive) [ 2019-01-11 ]

No, I agree after looking through the code more. To be sure we can retest this after the fix for 2009 is ready.

Comment by Daniel Lee (Inactive) [ 2019-01-24 ]

closing duplicate ticket

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