[jira] [Resolved] (IMPALA-5058) Improve concurrency of DDL/DML operations during catalog updates

["Dimitris Tsirogiannis (JIRA)" <ji...@apache.org>]

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

Dimitris Tsirogiannis resolved IMPALA-5058.
-------------------------------------------
    Resolution: Won't Fix

> Improve concurrency of DDL/DML operations during catalog updates
> ----------------------------------------------------------------
>
>                 Key: IMPALA-5058
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5058
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>    Affects Versions: Impala 2.5.0, Impala 2.6.0, Impala 2.7.0
>            Reporter: Dimitris Tsirogiannis
>            Assignee: Dimitris Tsirogiannis
>              Labels: catalog-server, performance, usability
>
> Currently, long running DDL/DML operations can block other operations from making progress if they run concurrently with the getCatalogObjects() call that creates catalog updates. The reason is that while getCatalogObjects() holds the lock for its entire duration and also tries to acquire the locks for the tables it processes. If that operation is blocked by another operation on a table then any other, unrelated, catalog write operation cannot make any progress as it cannot acquire the catalog lock which is held by getCatalogObjects().



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)