Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

After opening kerberos, impala can't access kudu table

avatar
Explorer

After opening kerberos, impala can't access kudu table。

CDH6.0.0

 

[ghqbigdata3:21000] dm_odata_phq> select * from total_record limit 10;
Query: select * from total_record limit 10
Query submitted at: 2019-10-09 09:52:58 (Coordinator: http://ghqbigdata3:25000)
ERROR: AnalysisException: Failed to load metadata for table: 'total_record'
CAUSED BY: TableLoadingException: Error loading metadata for Kudu table impala::dm_odata_phq.total_record
CAUSED BY: ImpalaRuntimeException: Error opening Kudu table 'impala::dm_odata_phq.total_record', Kudu error: cannot re-acquire authentication token after 5 attempts

 

I1009 17:17:20.229892 48700 Frontend.java:935] Analyzing query: select * from cust_info limit 10
I1009 17:17:20.334491 48700 jni-util.cc:230] org.apache.impala.common.AnalysisException: Failed to load metadata for table: 'cust_info'
        at org.apache.impala.analysis.Analyzer.resolveTableRef(Analyzer.java:581)
        at org.apache.impala.analysis.FromClause.analyze(FromClause.java:59)
        at org.apache.impala.analysis.SelectStmt.analyze(SelectStmt.java:155)
        at org.apache.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:424)
        at org.apache.impala.analysis.AnalysisContext.analyzeAndAuthorize(AnalysisContext.java:393)
        at org.apache.impala.service.Frontend.createExecRequest(Frontend.java:946)
        at org.apache.impala.service.JniFrontend.createExecRequest(JniFrontend.java:156)
Caused by: org.apache.impala.catalog.TableLoadingException: Error loading metadata for Kudu table impala::dm_odata_phq.cust_info
CAUSED BY: ImpalaRuntimeException: Error opening Kudu table 'impala::dm_odata_phq.cust_info', Kudu error: cannot re-acquire authentication token after 5 attempts
        at org.apache.impala.catalog.IncompleteTable.loadFromThrift(IncompleteTable.java:113)
        at org.apache.impala.catalog.Table.fromThrift(Table.java:311)
        at org.apache.impala.catalog.ImpaladCatalog.addTable(ImpaladCatalog.java:405)
        at org.apache.impala.catalog.ImpaladCatalog.addCatalogObject(ImpaladCatalog.java:294)
        at org.apache.impala.catalog.ImpaladCatalog.updateCatalog(ImpaladCatalog.java:201)
        at org.apache.impala.service.Frontend.updateCatalogCache(Frontend.java:228)
        at org.apache.impala.service.JniFrontend.updateCatalogCache(JniFrontend.java:175)
        at ========.<Remote stack trace on catalogd>: org.apache.impala.catalog.TableLoadingException: Error loading metadata for Kudu table impala::dm_odata_phq.cust_info
        at org.apache.impala.catalog.KuduTable.load(KuduTable.java:233)
        at org.apache.impala.catalog.TableLoader.load(TableLoader.java:80)
        at org.apache.impala.catalog.TableLoadingMgr$2.call(TableLoadingMgr.java:241)
        at org.apache.impala.catalog.TableLoadingMgr$2.call(TableLoadingMgr.java:238)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.impala.common.ImpalaRuntimeException: Error opening Kudu table 'impala::dm_odata_phq.cust_info', Kudu error: cannot re-acquire authentication token after 5 attempts
        at org.apache.impala.catalog.KuduTable.loadSchemaFromKudu(KuduTable.java:200)
        at org.apache.impala.catalog.KuduTable.load(KuduTable.java:230)
        ... 7 more
()
I1009 17:17:20.381866 48700 status.cc:125] AnalysisException: Failed to load metadata for table: 'cust_info'
CAUSED BY: TableLoadingException: Error loading metadata for Kudu table impala::dm_odata_phq.cust_info
CAUSED BY: ImpalaRuntimeException: Error opening Kudu table 'impala::dm_odata_phq.cust_info', Kudu error: cannot re-acquire authentication token after 5 attempts
    @           0x9da88a  impala::Status::Status()
    @           0xe7e51d  impala::JniUtil::GetJniExceptionMsg()
    @           0xd96ce0  impala::Frontend::GetExecRequest()
    @           0xdb4e74  impala::ImpalaServer::ExecuteInternal()
    @           0xdc085f  impala::ImpalaServer::Execute()
    @           0xdf84d5  impala::ImpalaServer::query()
    @          0x126e6d5  beeswax::BeeswaxServiceProcessor::process_query()
    @          0x126db8d  beeswax::BeeswaxServiceProcessor::dispatchCall()
    @           0x9b869a  apache::thrift::TDispatchProcessor::process()
    @           0xcee239  apache::thrift::server::TAcceptQueueServer::Task::run()
    @           0xce82b9  impala::ThriftThread::RunRunnable()
    @           0xce9132  boost::detail::function::void_function_obj_invoker0<>::invoke()
    @           0xeeefcf  impala::Thread::SuperviseThread()
    @           0xeefad3  boost::detail::thread_data<>::run()
    @          0x14a500a  thread_proxy
    @     0x7f984dac6e25  start_thread
    @     0x7f984d7f434d  __clone
I1009 17:17:20.381980 48700 impala-server.cc:1007] UnregisterQuery(): query_id=4741df2a3472748f:82f4fb300000000
I1009 17:17:20.381997 48700 impala-server.cc:1094] Cancel(): query_id=4741df2a3472748f:82f4fb300000000

 

1 REPLY 1

avatar
Rising Star

Hi 

Can you try restarting Impala service and regenerate Kerberos ticket and try to access tables. Check if that helps.

https://cloudera-portal.force.com/articles/KB_Article/TSB-2018-297


Regards,
Bhuvan