You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Vadim Lositski (JIRA)" <ji...@apache.org> on 2017/01/21 10:05:26 UTC
[jira] [Created] (ZEPPELIN-1995) Scheduled execution of JDBC
Interpreter fails with Kerberos-enabled Hive
Vadim Lositski created ZEPPELIN-1995:
----------------------------------------
Summary: Scheduled execution of JDBC Interpreter fails with Kerberos-enabled Hive
Key: ZEPPELIN-1995
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1995
Project: Zeppelin
Issue Type: Bug
Components: zeppelin-interpreter
Affects Versions: 0.6.2, 0.6.1, 0.6.0
Environment: HDP 2.5.3, Zeppelin 0.6.0
Reporter: Vadim Lositski
We have following paragraph, with Hive configured as default JDBC datasource
{code}
%jdbc
select current_timestamp
{code}
Kerberos is enabled in our cluster, interpreter is configured to use keytab and everything works fine when run from UI
However, when notebook is scheduled to run as a cron job periodically following exception occurs.
{code}java.sql.SQLException: Could not open client transport for any of the Server URI's in ZooKeeper: GSS initiate failed
class org.apache.zeppelin.interpreter.InterpreterException
org.apache.zeppelin.jdbc.JDBCInterpreter.getConnection(JDBCInterpreter.java:250)
org.apache.zeppelin.jdbc.JDBCInterpreter.getStatement(JDBCInterpreter.java:275){code}
I suspect it is because of a fact that Kerberos ticket is initialized when interpreter is started and not available in the scheduler thread or it is expired and not refreshed again.
Please ensure that Kerberos ticket is always available for scheduler thread and refreshed if needed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)