Cloudera Community
Announcements
Celebrating as our community reaches 100,000 members! Thank you!
hrishi1dypim
user rank
Explorer

Re: Caused by: org.apache.thrift.transport.TTransp...

by Explorer in Support Questions
‎05-17-2018 12:37 AM
‎05-17-2018 12:37 AM
the reported issue is in PROD though we have got the error in UAT too but very rare. we are having 15 JDBC  connection  in connection pool.  ... View more

Re: Caused by: org.apache.thrift.transport.TTransp...

by Explorer in Support Questions
‎05-16-2018 11:43 PM
‎05-16-2018 11:43 PM
just a correction, we are using haproxy in UAT env but for PROD we are using  VIP which is created by infrastructure team. here is the UAT config:   bash-4.1$ vi haproxy-cdh.cfg user impala group impala daemon # turn on stats unix socket #stats socket /var/lib/haproxy/stats #--------------------------------------------------------------------- # common defaults that all the 'listen' and 'backend' sections will # use if not designated in their block # # You might need to adjust timing values to prevent timeouts. #--------------------------------------------------------------------- defaults # mode http # option httplog option dontlognull option http-server-close option redispatch retries 3 maxconn 1000 timeout connect 300000 timeout client 300000 timeout server 300000 # # This sets up the admin page for HA Proxy at port 25002. # listen stats :25002 balance mode http stats enable stats auth username:password # This is the setup for Impala. Impala client connect to load_balancer_host:25003. # HAProxy will balance connections among the list of servers listed below. # The list of Impalad is listening at port 21000 for beeswax (impala-shell) or original ODBC driver. # For JDBC or ODBC version 2.x driver, use port 21050 instead of 21000. #listen impala :25053 listen impala :25003 timeout client 3600000 timeout server 3600000 balance leastconn   ... View more

Re: Caused by: org.apache.thrift.transport.TTransp...

by Explorer in Support Questions
‎05-16-2018 11:29 PM
‎05-16-2018 11:29 PM
yes i am using haproxy where i have configured my all impalad nodes and this url is used by jdbc connection. ... View more

Re: Caused by: org.apache.thrift.transport.TTransp...

by Explorer in Support Questions
‎05-16-2018 11:18 PM
‎05-16-2018 11:18 PM
yes,but still get this problem many times. ... View more

Caused by: org.apache.thrift.transport.TTransportE...

by Explorer in Support Questions
‎12-26-2017 04:04 AM
‎12-26-2017 04:04 AM
I get below error sometimes while running Impala query  through JDBC connection using Hive jars:   java.sql.SQLException: Error while cleaning up the server resources                 at org.apache.hive.jdbc.HiveConnection.close(HiveConnection.java:580)                 at gxs.core.hadoop$with_impala_connection_STAR_.invoke(Unknown Source) Caused by: org.apache.thrift.transport.TTransportException: java.net.SocketException: Broken pipe                 at org.apache.thrift.transport.TIOStreamTransport.flush(TIOStreamTransport.java:161)                 at org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:65)                 at org.apache.hive.service.cli.thrift.TCLIService$Client.send_CloseSession(TCLIService.java:173)                 at org.apache.hive.service.cli.thrift.TCLIService$Client.CloseSession(TCLIService.java:165)                 at org.apache.hive.jdbc.HiveConnection.close(HiveConnection.java:578)                 ... 25 more Caused by: java.net.SocketException: Broken pipe                 at java.net.SocketOutputStream.socketWrite0(Native Method)                 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)                 at java.net.SocketOutputStream.write(SocketOutputStream.java:136)                 at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)                 at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)                 at org.apache.thrift.transport.TIOStreamTransport.flush(TIOStreamTransport.java:159)                 ... 29 more   How to resolve this ? ... View more
Labels:

Re: Impala query does not respond,seems stuck or g...

by Explorer in Support Questions
‎09-26-2017 12:46 AM
‎09-26-2017 12:46 AM
have seen the execution summary ,its taking 15 mins and after that query is getting cancelled.have already done compute stats for involved tables. there is no memory problem as it shows consumption 340 MB out of 35 GB of memory. ... View more

Re: Getting Error : Spilling has been disabled due...

by Explorer in Support Questions
‎09-19-2017 11:41 PM
‎09-19-2017 11:41 PM
my point is why impala is not trying to use the directory which i am providing like this :  ./impala-server start --scratch_dirs="/data/impala-scratch"   why its still expecting /tmp/impala-scratch" ?   How to resolve it ? ... View more

Re: Getting Error : Spilling has been disabled due...

by Explorer in Support Questions
‎09-19-2017 12:48 AM
‎09-19-2017 12:48 AM
I cant see any error related to scratch dir setup.i can see only : Could not remove and recreate directory /tmp/impala-scratch: cannot use it for scratch. Error was: Encountered error removing directory '/tmp/impala-scratch': Operation not permitted.   looks there is no impact of provided path while starting. can you tell if my command is correct or do i need to use other command for that ? ... View more

Getting Error : Spilling has been disabled due to ...

by Explorer in Support Questions
‎09-18-2017 03:28 AM
‎09-18-2017 03:28 AM
Hello,     I am using : impalad version 2.7.0-cdh5.9.0  and for few days my impala query is getting failed with the error : java.sql.SQLException: Spilling has been disabled due to no usable scratch space. Please specify a usable scratch space location via the --scratch_dirs impalad flag.   the weired thing is that i have done all the possible  solutions as below,  but still why i am getting the error :   1. have created /tmp//tmp/impala-scratch directory on all the impalad nodes. 2. have created /tmp/impala-scratch on hdfs also 3. have created a folder /data/impala-scratch and startimg impala-server like below : ./impala-server start --scratch_dirs="/data/impala-scratch"   and scratch folders have enough space and write permission. kindly help to resolve this problem , this problem is in PROD env. ... View more
Labels:

Cloudera manager/agent installation without root u...

by Explorer in Support Questions
‎06-15-2017 03:58 AM
‎06-15-2017 03:58 AM
Hello,   I have setup hadoop cluster on my DeV/UAT/PROD env using the tar balls manually with fid. now its getting difficult to maintain or add new datanode or new software as cluster size is growing. also we are not allowed to login through fid so frequantly on PROD env. Cloudera manager/agent requires root user access to install,if  i had this; my work would have been easier.   We have policy that what all softwares can be installed using root access and what not. so cant install cloudera manager/agent using root access by Unix Sa.   Is it possible to install Clouder manager/Agents using fid  or non root,non root group users ? Kindly help. ... View more
Labels:
Contact Me
Online
Offline
Last Visited
‎09-26-2019 11:37 PM
Community Statistics
Member Since ‎09-29-2016 03:07 AM
Last Visited ‎09-26-2019 11:37 PM
Posts 60