Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
23.02.4
-
2023-10, 2023-11, 2023-12
Description
PrimProc runs multiple parts of a query called primitive jobs.
There is a problem that causes primitive in-memory representation to become corrupted so it cannot be stopped and doesn't go away from PP execution thread pool. When there is a certain number of such primitives it is enough to get busy all worker threads in PP.
Effectively this looks like all future query are stuck.
The issue hits our CI. One of the customers also suffers from the same issue.
Attachments
Issue Links
- relates to
-
MCOL-5801 Queries Hung | PrimProc <-> Storagemanager | Unknown error code in response
- Open
-
MCOL-5559 Shmem segment remap causes SEGV in ExtentMapIndexImpl::find
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...