Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Error in semantic analysis: Lock manager could not be initialized ...

Solved Go to solution

Error in semantic analysis: Lock manager could not be initialized ...

Explorer

sometimes, error message on thrift server console:

FAILED: Error in semantic analysis: Lock manager could not be initialized, check hive.lock.manager Check hive.zookeeper.quorum and hive.zookeeper.client.port

 

background:

1. sqlserver's linked server ----odbc---->hive thrift server.

2. just run select * from sqlserver on hive tables/views, no error; when build cube by sqlserver, then this error.

 

any suggestions?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Error in semantic analysis: Lock manager could not be initialized ...

Contributor


Hi,

 

Are you using Hive Server 1 or Hive Server 2?  We strongly recommend Hive Server 2. If you are using HS2 it sounds like the Table Lock Manager is not correctly configured. The steps to do so are located on this page:

 

http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/c...

2 REPLIES 2

Re: Error in semantic analysis: Lock manager could not be initialized ...

Contributor


Hi,

 

Are you using Hive Server 1 or Hive Server 2?  We strongly recommend Hive Server 2. If you are using HS2 it sounds like the Table Lock Manager is not correctly configured. The steps to do so are located on this page:

 

http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/c...

Re: Error in semantic analysis: Lock manager could not be initialized ...

Explorer

I am using hive server 1.

OK, I will try hive server 2.

Thanks.