[jira] [Resolved] (IMPALA-7376) Impala hits a DCHECK if a fragment instance fails to initialize the filter bank

["Sailesh Mukil (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sailesh Mukil resolved IMPALA-7376.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0

> Impala hits a DCHECK if a fragment instance fails to initialize the filter bank
> -------------------------------------------------------------------------------
>
>                 Key: IMPALA-7376
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7376
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>            Reporter: Sailesh Mukil
>            Assignee: Sailesh Mukil
>            Priority: Critical
>              Labels: crash
>             Fix For: Impala 3.1.0
>
>
> While Prepare()-ing a fragment instance, if we fail to initialize the runtime filter bank, we will exit FIS::Prepare() without acquiring a thread token (AcquireThreadToken()):
> https://github.com/apache/impala/blob/316b17ac55adb3d1deeb1289b4045688269b201d/be/src/runtime/fragment-instance-state.cc#L135-L139
> FIS::Finalize() is called *always* regardless of whether the fragment instance succeeded or failed. And FIS::Finalize() tries to ReleaseThreadToken() even though it might not have gotten acquired:
> https://github.com/apache/impala/blob/316b17ac55adb3d1deeb1289b4045688269b201d/be/src/runtime/fragment-instance-state.cc#L464
> , causing a DCHECK to be hit.
> This was found while I was adding global debug actions (IMPALA-7046) to the FIS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org