You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2019/03/18 23:58:00 UTC

[jira] [Resolved] (IMPALA-5393) Regexp should use THREAD_LOCAL context rather than FRAGMENT_LOCAL

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

Todd Lipcon resolved IMPALA-5393.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.3.0

> Regexp should use THREAD_LOCAL context rather than FRAGMENT_LOCAL
> -----------------------------------------------------------------
>
>                 Key: IMPALA-5393
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5393
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.8.0
>            Reporter: Doug Cameron
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: Impala 3.3.0
>
>
> The RE2 library uses mutex locking around some internal state structures.  This causes severe lock contention and lack of CPU scaling on the regexp string function.
> Switching to THREAD_LOCAL context will remove the contention.
> We could add a query option to select between FRAGMENT_LOCAL vs THREAD_LOCAL but that seems overkill as the context is not huge.
>  



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