hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20801) ACID: Allow DbTxnManager to ignore non-ACID table locking
Date Mon, 04 Mar 2019 21:35:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783794#comment-16783794
] 

Ashutosh Chauhan commented on HIVE-20801:
-----------------------------------------

Now we only have ACID tables or insert-only (MM) tables or external tables. If etl is via
spark or sqoop, those tables should be external and then there will be no locking on them.


> ACID: Allow DbTxnManager to ignore non-ACID table locking
> ---------------------------------------------------------
>
>                 Key: HIVE-20801
>                 URL: https://issues.apache.org/jira/browse/HIVE-20801
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking, Transactions
>    Affects Versions: 4.0.0
>            Reporter: Gopal V
>            Assignee: Gopal V
>            Priority: Major
>              Labels: Branch3Candidate, TODOC
>         Attachments: HIVE-20801.1.patch, HIVE-20801.2.patch, HIVE-20801.2.patch, HIVE-20801.3.patch
>
>
> Enabling ACIDv1 on a cluster produces a central locking bottleneck for all table types,
which is not always the intention.
> The Hive locking for non-acid tables are advisory (i.e a client can write/read without
locking), which means that the implementation does not offer strong consistency despite the
lock manager consuming resources centrally.
> Disabling this lock acquisition would improve the performance of non-ACID tables co-existing
with a globally configured DbTxnManager implementation.



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

Mime
View raw message