You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2015/11/12 09:14:10 UTC

[jira] [Updated] (KYLIN-1139) Hive job not starting due to error "conflicting lock present for default mode EXCLUSIVE "

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

Shaofeng SHI updated KYLIN-1139:
--------------------------------
    Description: 
some kylin hive jobs are not starting due to "conflicting lock present for default mode EXCLUSIVE ", the log in the first cube build step is similar to :

{code}
conflicting lock present for default mode EXCLUSIVE 
conflicting lock present for default mode EXCLUSIVE 
conflicting lock present for default mode EXCLUSIVE 
conflicting lock present for default mode EXCLUSIVE 
FAILED: Error in acquiring locks: Locks on the underlying objects cannot be acquired. retry after some time 
{code}

This is related with Hive's concurrency model:
https://cwiki.apache.org/confluence/display/Hive/Locking

If the underlying table is locked by other users, Kylin will not be able to read from it. Hadoop admin suggest to set "hive.support.concurrency" as false and rerun the job. 

  was:
some kylin hive jobs are not starting due to "conflicting lock present for default mode EXCLUSIVE ", the log in the first cube build step is similar to :

{code}
conflicting lock present for default mode EXCLUSIVE 
conflicting lock present for default mode EXCLUSIVE 
conflicting lock present for default mode EXCLUSIVE 
conflicting lock present for default mode EXCLUSIVE 
FAILED: Error in acquiring locks: Locks on the underlying objects cannot be acquired. retry after some time 
{code}


> Hive job not starting due to error "conflicting lock present for default mode EXCLUSIVE "
> -----------------------------------------------------------------------------------------
>
>                 Key: KYLIN-1139
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1139
>             Project: Kylin
>          Issue Type: Bug
>    Affects Versions: v1.1, v1.0
>            Reporter: Shaofeng SHI
>            Assignee: Shaofeng SHI
>             Fix For: v2.0, v1.2
>
>
> some kylin hive jobs are not starting due to "conflicting lock present for default mode EXCLUSIVE ", the log in the first cube build step is similar to :
> {code}
> conflicting lock present for default mode EXCLUSIVE 
> conflicting lock present for default mode EXCLUSIVE 
> conflicting lock present for default mode EXCLUSIVE 
> conflicting lock present for default mode EXCLUSIVE 
> FAILED: Error in acquiring locks: Locks on the underlying objects cannot be acquired. retry after some time 
> {code}
> This is related with Hive's concurrency model:
> https://cwiki.apache.org/confluence/display/Hive/Locking
> If the underlying table is locked by other users, Kylin will not be able to read from it. Hadoop admin suggest to set "hive.support.concurrency" as false and rerun the job. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)