About jarourbtb

kakanab · ‎10-20-2017

We have workaround first point is inplace but we have experienced connection establishment issues from webserver to impala with below error. It got fixed itself after couple of hours and would like to know what causes this behavior. [Simba][ImpalaJDBCDriver](500176) Error connecting to HiveServer2, please verify connection details. Please help us to understand what causes this issue. Thank you, Aj

jarourbtb · ‎04-25-2016

Thank you very much, Tim and Ivan. I have tested on customer system and with "set disable_codegen=1;" the query does NOT crash the whole impala cluster anymore. I will inform the customer and provide him with a link to this discussion

Lars Volker · ‎04-22-2016

Hi Jaro, no, the JDBC and ODBC drivers are not open source projects. Best wishes, Lars

jarourbtb · ‎04-21-2016

thank you, SparkeyG! for the YARN environment snippet should I add the same string (PYSPARK_PYTHON)?

jarourbtb · ‎01-14-2016

well, this was indeed unnecessary strugle... 😞 I found the root cause in the logs of the now active namenode ("java.io.IOException: Cannot run program "/etc/hadoop/conf/rack-topology.sh") when I enabled the High Availability in the cluster as a part of the exercises required by the admin course I simply forgot to provide the new namenode with the rack-topology.sh script (changing the topology was another prior exercise). now all hdfs commands can be run from both namenodes

Online	Offline
Last Visited	‎06-05-2016 01:30 PM

Member Since	‎04-04-2016 08:24 AM
Last Visited	‎06-05-2016 01:30 PM
Posts	17
Kudos received	6

Cloudera Community

Re: hdfs commands not working from StandBy namenod...

Re: IMPALA JDBC connection

Re: query causes Impala to crash

Re: ClouderaClouderaImpalaJDBCDriver.lic missing

Re: Change Python path

Re: hdfs commands not working from StandBy namenod...