on 06-24-2017 10:21 PM
I'm using Vora 1.4 on an Cloudera test-cluster on AWS and getting the following error while connecting to Vora tools:
Error while compiling statement: FAILED: SemanticException Table not found 'SYS_TABLES' with error code 10001, status ERROR_STATUS
All services are up, also the thriftserver is running and I tried several ports without success.
Kindly advise.
see the comment on the first answer.
I can imagine, that there is a problem with authentication
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you running CDH 5.11? If so, you could be running into a known issue that was introduced with the Spark version that comes with CDH5.11. This should be fixed in Vora 1.4 Patch 2.
As a workaround you will have to download Spark 1.6.2 from Apache Spark's website (http://spark.apache.org/downloads.html), extract the package on the host where Vora Thriftserver is running (you can check this in Vora Manager UI) and set the Spark home directory in the Vora Thriftserver settings to point the 1.6.2 installation.
I'm still testing.
However I found in the vora thriftserver logs, that before the error is thrown there is a warning potentially giving a hint on the root-cause. The error including this warning is (check the first line with WARN):
17/07/07 10:27:09 WARN security.UserGroupInformation: PriviledgedActionException as:vora (auth:SIMPLE) cause:org.apache.hive.service.cli.HiveSQLException: Error while compiling statement: FAILED: SemanticException [Error 10001]: Line 1:23 Table not found 'SYS_SESSION_CONTEXT'
17/07/07 10:27:09 WARN thrift.ThriftCLIService: Error executing statement:
org.apache.hive.service.cli.HiveSQLException: Error while compiling statement: FAILED: SemanticException [Error 10001]: Line 1:23 Table not found 'SYS_SESSION_CONTEXT'
at org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:400)
at org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:188)
at org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:267)
at org.apache.hive.service.cli.operation.Operation.run(Operation.java:337)
at org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:439)
at org.apache.hive.service.cli.session.HiveSessionImpl.executeStatement(HiveSessionImpl.java:405)
at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:78)
at org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:36)
at org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:63)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1920)
at org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:59)
at com.sun.proxy.$Proxy40.executeStatement(Unknown Source)
at org.apache.hive.service.cli.CLIService.executeStatement(CLIService.java:257)
at org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:501)
at org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1313)
at org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1298)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.hadoop.hive.ql.parse.SemanticException: Line 1:23 Table not found 'SYS_SESSION_CONTEXT'
Hi,
I'm using AWS behind a proxy, so although, that the public IP addresses changes, the private one does not. I do not have problems to access Vora Manager, Cloudera Manager, Cloudera Director, HUE, ....
Even I can connect to the Vora Tools, however, the connection status shows the error message posted.
I'm sure, that the problem lies somewhere else. What I do not understand is: Which table is tried to be accessed in which database?
Table not found 'SYS_TABLES' with error code 10001, status ERROR_STATUS
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you using VPC in AWS? If not, and your ip addresses change for the nodes in your cluster, you will run into strange problems.
If IP addresses have changed since you installed Vora, the Vora troubleshooting guide explains how you can fix the problem:
--Jason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
as expected, I followed the steps without any impact on the error message:
In vora manager all services are started:
Vora tools, the error message still persists:
Error while compiling statement: FAILED: SemanticException [Error 10001]: Line 1:70 Table not found 'SYS_TABLES' with error code 10001, status ERROR_STATUS
User | Count |
---|---|
76 | |
10 | |
8 | |
8 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.