The "Clock skew too great" error in your release (which is out of maintenance due to its age) usually happens when the daemon is overloaded and KRPC is *not* enabled (--use_krpc=false in the Impala safety valve). That is likely why you see those errors. Although - certain overload conditions trigger unusual errors regardless. That is likely why you get the rejection on any client. You can try several things: a. make sure "--use_krpc=false" is not in the current Impala configs b. adjust the workload c. if you get the error with near zero load *after the coordinator restart* that definitely points at a network issue as I have alluded to before d. make sure the coordinator host's kernel settings are adequate: kernel.pid_max = 1048480 vm.max_map_count = 1048480 kernel.pid_max = 2000000 vm.max_map_count = 8000000 ... View more

Hello- The error means that the socket connection cannot be instantiated or was closed by the peer. In the setup, the most likely reasons are: a. the coordinator to which Hue is trying to connect is down b. the coordinator to which hue is trying to connect has its front end connections pool maxed out c. the coordinator is down or not listening on the port forwarded by the loadbalancer d. a network connectivity issue (including a faulty loadbalancer) A good alternative test would be to run an impaal-shell connection to the same coordinator: impala-shell -b <loadbalancer FQDN> -i <coordinator FQDN> ..... <the rest of the impala-shell parameters> - if the same issue cannot be reproduced then the issue is likely on the Hue side (network as mentioned and/or a port to which Hue is configured to connect), else - the issue is likely with the coordinator itself (it cannot accept new connections - front end connection pool is maxed out or the daemon itself is in a bad state. Usually restart should help then. There is also a slight chance that your kerberos is misconfigured - if the issue happens only when you run a Hue connection.   As you can see there may be many reasons to what is happening. We usually investigate these kinds of issues via analyzing logs and traces in Cloudera Support tickets.   ... View more

Hello-   Pasting here the reply from 6 yrs ago, which I still find relevant: Running Impala query over driver from Spark is not currently supported by Cloudera. Why don't you just use SparkSQL instead? Why need to have extra layer of impala here? ... View more

Hi- There are number of things to note here: Replication factor seems to be 1 for above listed tables which is not a good setting given customer is facing failures and running into unavailability situation. This needs to be at least 3 in order to deal with transient errors or even a permanent data loss on a replica. If the ksck report is showing every TS up and running, where is the problem now? Is there any tablet which is not accessible (for read/write) to the user? You could list all the tablets using "kudu table list <master_addresses> --list_tablets" and search for the tablet server hosting the replica in question from the output; you can search for tablet uuid in old logs from the time when issue was seen, from there corresponding tablet server entry should have logged at some point. But - generally speaking - if your KSCK is fixed and clean - let's say, it finished bootstrapping and/or copying after some time - and you still see INSERT problems from Spark - you need to open a case with Cloudera since the issue may require certain configs' evaluation and tuning. ... View more

Hello- Looks like you did not follow the setup instructions in https://docs.cloudera.com/documentation/other/connectors/impala-jdbc/2-6-23/Cloudera-JDBC-Driver-for-Impala-Install-Guide.pdf. Especially when it comes to referencing Driver Libraries, like on p.8 etc. Please re-visit the document and follow the steps to have the Driver Jar "visible" to the Windows applications. HTH. ... View more

Hello- Please see https://impala.apache.org/docs/build/html/topics/impala_complex_types.html#complex_sample_schema for the correct schema definitions as well as examples of queries against complex data structures like ARRAY and MAP (which is implemented very similar to ARRAY in Impala). Let me know if that helps.   ... View more

Hello- See https://docs.cloudera.com/documentation/other/connectors/impala-jdbc/2-6-23/Cloudera-JDBC-Driver-for-Impala-Install-Guide.pdf for instructions on how to configure JAAS for JDBC. P.16, for example. Also -- just search for 'JAAS' the whole document, and follow the steps, as applicable.   ... View more