Member since
03-12-2014
29
Posts
4
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
32808 | 10-19-2015 10:14 AM | |
12659 | 05-16-2015 09:40 AM | |
7647 | 01-15-2015 08:11 AM |
10-19-2015
10:14 AM
1 Kudo
Solved. According to this link, the temporary workaround is to specify use_get_log_api=true in the beeswax section of the hue.ini configuration file. The “Server does not support GetLog()” error will still show, but the SQL statement will be executed.
... View more
10-19-2015
08:18 AM
When running SQL statements through Hue against one of our Hadoop clusters running Hortonworks 2.2.4.2-2, we keep getting the following error: Fetching results ran into the following error(s): Couldn't find log associated with operation handle: OperationHandle [opType=EXECUTE_STATEMENT, getHandleIdentifier()=40fad20f-8413-4bd1-b6c8-9f0e858e3262] The query log shows the following: Bad status for request TFetchResultsReq(fetchType=1, operationHandle=TOperationHandle(hasResultSet=True, modifiedRowCount=None, operationType=0, operationId=THandleIdentifier(secret='\xdf\xb6\xb0\xdeM\xdfH~\x88bu]w\x96Q\xae', guid='@\xfa\xd2\x0f\x84\x13K\xd1\xb6\xc8\x9f\x0e\x85\x8e2b')), orientation=4, maxRows=-1): TFetchResultsResp(status=TStatus(errorCode=0, errorMessage="Couldn't find log associated with operation handle: OperationHandle [opType=EXECUTE_STATEMENT, getHandleIdentifier()=40fad20f-8413-4bd1-b6c8-9f0e858e3262]", sqlState=None, infoMessages=["*org.apache.hive.service.cli.HiveSQLException:Couldn't find log associated with operation handle: OperationHandle [opType=EXECUTE_STATEMENT, getHandleIdentifier()=40fad20f-8413-4bd1-b6c8-9f0e858e3262]:45:44", 'org.apache.hive.service.cli.operation.OperationManager:getOperationLogRowSet:OperationManager.java:257', 'org.apache.hive.service.cli.session.HiveSessionImpl:fetchResults:HiveSessionImpl.java:656', 'sun.reflect.NativeMethodAccessorImpl:invoke0:NativeMethodAccessorImpl.java:-2', 'sun.reflect.NativeMethodAccessorImpl:invoke:NativeMethodAccessorImpl.java:57', 'sun.reflect.DelegatingMethodAccessorImpl:invoke:DelegatingMethodAccessorImpl.java:43', 'java.lang.reflect.Method:invoke:Method.java:606', 'org.apache.hive.service.cli.session.HiveSessionProxy:invoke:HiveSessionProxy.java:79', 'org.apache.hive.service.cli.session.HiveSessionProxy:access$000:HiveSessionProxy.java:37', 'org.apache.hive.service.cli.session.HiveSessionProxy$1:run:HiveSessionProxy.java:64', 'java.security.AccessController:doPrivileged:AccessController.java:-2', 'javax.security.auth.Subject:doAs:Subject.java:415', 'org.apache.hadoop.security.UserGroupInformation:doAs:UserGroupInformation.java:1628', 'org.apache.hadoop.hive.shims.HadoopShimsSecure:doAs:HadoopShimsSecure.java:536', 'org.apache.hive.service.cli.session.HiveSessionProxy:invoke:HiveSessionProxy.java:60', 'com.sun.proxy.$Proxy25:fetchResults::-1', 'org.apache.hive.service.cli.CLIService:fetchResults:CLIService.java:450', 'org.apache.hive.service.cli.thrift.ThriftCLIService:FetchResults:ThriftCLIService.java:587', 'org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults:getResult:TCLIService.java:1553', 'org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults:getResult:TCLIService.java:1538', 'org.apache.thrift.ProcessFunction:process:ProcessFunction.java:39', 'org.apache.thrift.TBaseProcessor:process:TBaseProcessor.java:39', 'org.apache.thrift.server.TServlet:doPost:TServlet.java:83', 'org.apache.hive.service.cli.thrift.ThriftHttpServlet:doPost:ThriftHttpServlet.java:101', 'javax.servlet.http.HttpServlet:service:HttpServlet.java:727', 'javax.servlet.http.HttpServlet:service:HttpServlet.java:820', 'org.eclipse.jetty.servlet.ServletHolder:handle:ServletHolder.java:565', 'org.eclipse.jetty.servlet.ServletHandler:doHandle:ServletHandler.java:479', 'org.eclipse.jetty.server.session.SessionHandler:doHandle:SessionHandler.java:225', 'org.eclipse.jetty.server.handler.ContextHandler:doHandle:ContextHandler.java:1031', 'org.eclipse.jetty.servlet.ServletHandler:doScope:ServletHandler.java:406', 'org.eclipse.jetty.server.session.SessionHandler:doScope:SessionHandler.java:186', 'org.eclipse.jetty.server.handler.ContextHandler:doScope:ContextHandler.java:965', 'org.eclipse.jetty.server.handler.ScopedHandler:handle:ScopedHandler.java:117', 'org.eclipse.jetty.server.handler.HandlerWrapper:handle:HandlerWrapper.java:111', 'org.eclipse.jetty.server.Server:handle:Server.java:349', 'org.eclipse.jetty.server.AbstractHttpConnection:handleRequest:AbstractHttpConnection.java:449', 'org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler:content:AbstractHttpConnection.java:925', 'org.eclipse.jetty.http.HttpParser:parseNext:HttpParser.java:857', 'org.eclipse.jetty.http.HttpParser:parseAvailable:HttpParser.java:235', 'org.eclipse.jetty.server.AsyncHttpConnection:handle:AsyncHttpConnection.java:76', 'org.eclipse.jetty.io.nio.SelectChannelEndPoint:handle:SelectChannelEndPoint.java:609', 'org.eclipse.jetty.io.nio.SelectChannelEndPoint$1:run:SelectChannelEndPoint.java:45', 'java.util.concurrent.ThreadPoolExecutor:runWorker:ThreadPoolExecutor.java:1145', 'java.util.concurrent.ThreadPoolExecutor$Worker:run:ThreadPoolExecutor.java:615', 'java.lang.Thread:run:Thread.java:745'], statusCode=3), results=None, hasMoreRows=None It's interesting to notice that the same SELECT statements run fine when the tables are browsed using the Metastore Manager. I also want to point out that our cluster is using transport mode for Hive set to HTTP (instead of BINARY). That was one of the resons why we switched from Hue 3.7.1 to 3.8.1 as we found some info that stated support for HTTP transport mode was not available at 3.7.1. Any help would be greatly appreciated. Thanks!
... View more
Labels:
- Labels:
-
Apache Hadoop
-
Apache Hive
-
Cloudera Hue
-
Security
05-18-2015
06:49 AM
Good to know, thanks! Hue is indeed using LDAP to authenticate against HS2. I think it would be helpful to have a message in the log to point admins in the right direction 🙂
... View more
05-18-2015
06:44 AM
Yes, I have those two set, along with a bunch of others under the Security tab in the Hue configuration.
... View more
05-18-2015
06:35 AM
That's what I thought too. However, the problem disappeared only after setting the following properties via Cloudera Manager in the Impala Command Line Argument Advanced Configuration Snippet (Safety Valve): -ldap_allow_anonymous_binds=false -ldap_domain= -ldap_manual_config=false -ldap_passwords_in_clear_ok=true -ldap_tls=false -ldap_uri= I know the option values for some of them are the default ones, but I chose to add the options to the Safety Valve anyway for completeness.
... View more
05-16-2015
09:40 AM
Problem solved. Rebooting the cluster servers didn’t fix the issue. The problem was due to Hue being configured with LDAP. Even though I didn’t find anything that says otherwise, I didn’t think that Having LDAP implemented for Hue required Impala too to be configured for LDAP. After doing that the misconfiguration message disappears, and everything works fine. Thanks again for your help!
... View more
05-15-2015
10:56 AM
Let me run a full restart in case something is hosed somewhere. I'll update the post as soon as I'm done. Thanks for your help.
... View more
05-15-2015
10:39 AM
As I mentioned earlier, the impala shell works fine. I can connect and work with Impala without any problems.
... View more
05-15-2015
10:25 AM
Thanks. Server_name is one of the servers where the impalad deamon is running. The port number is the default one (21050).
... View more