@JoaquinS Your CM agent config file does not have TLS enabled, but the CM server configuration has.  I would suggest to disable the Use TLS Encryption for Agents, Use TLS Authentication of Agents to Server, Verify Agent Hostname Against Certificate settings and restart CM to proceed to make the installation work in a first step.   Once that is done, please follow the steps in this documentation chapter to enable TLS encryption for CM agent communication. ... View more

could you share the steps fo jce policy file     i have install in /usr/java/jdk1.8.0_171/jre/bin/security/US_export_policy.jar   /usr/java/jdk1.8.0_171/jre/bin/security/local_policy.jar ... View more

Thanks a lot for the info ... View more

@Prav,   More or less, I think we are on the same page.  One thing to keep in mind, too is the offset so that you can make sure you are seeing all the results in the timeperiod.   For example:   Return the first 1000 queries starting from most recent:   https://hostname:7183/api/v17/clusters/cluster/services/impala/impalaQueries?from=2018-07-09T12:59:32.776Z&to=2018-07-10&limit=1000   Retrun the next 1000 queries:   https://hostname:7183/api/v17/clusters/cluster/services/impala/impalaQueries?from=2018-07-09T12:59:32.776Z&to=2018-07-10&limit=1000&offset=1000   Return the next 1000:   https://hostname:7183/api/v17/clusters/cluster/services/impala/impalaQueries?from=2018-07-09T12:59:32.776Z&to=2018-07-10&limit=1000&offset=2000   (Keep doing this until you get 0 results) If you get 0 results AND you also have a warning, that means you have another partition to traverse. In that case, you would use the date/time in the warning to populate the "to" parameter in the next query (assuming the warnings show the date time 2018-07-10T01:16:17.434Z):   https://hostname:7183/api/v17/clusters/cluster/services/impala/impalaQueries?from=2018-07-09T12:59:32.776Z&to=2018-07-10T01:16:17.434Z&limit=1000   If the number of queries is equal to the limit, increment the offset to return the next 1000:   https://hostname:7183/api/v17/clusters/cluster/services/impala/impalaQueries?from=2018-07-09T12:59:32.776Z&to=2018-07-10T01:16:17.434Z&limit=1000&offset=1000   and repeat until you get 0 queries returned.   If you get another warnings date/time, replace the "to" parameter value with it and repeat. If you get 0 results and 0 warnings, there are no more queries to retrieve.   NOTE:  While you are doing all these queries, running queries may complete, so it is a good idea to specify an initial "to" date that is a little bit in the past if you want consistent results. ... View more

If you want to use spark2-shell and spark2-submit, you don't have to set those ENV variables. I set it because I wanted to point the current spark-shell/submit to spark2.   This should be done in all the nodes that you want to use the shell and/or the submit.   I forgot to add the changes that I made for spark-sumbit. In these files:   /opt/cloudera/parcels/CDH-5.8.0-1.cdh5.8.0.p0.42/bin/spark-submit /opt/cloudera/parcels/CDH-5.8.0-1.cdh5.8.0.p0.42/lib/spark/bin/spark-submit Add this ENV var: SPARK_HOME=/opt/cloudera/parcels/SPARK2-2.1.0.cloudera1-1.cdh5.7.0.p0.120904/lib/spark2 ... View more

No one stopped or uninstalled the agent manually because I'm the only one that manages that server. What I did that day was reinstall a MySQL server, I don't know if that is related with this issue.   Running cloudera-scm-agent  seems that is was uninstalled: Failed to start cloudera-scm-agent.service: Unit cloudera-scm-agent.service failed to load: No such file or directory. So I reinstalled the agent and now is working.   Thanks ... View more

hi   were you able to resolve this problem?   ip-10-0-0-5.ec2.internal, executor 1): java.lang.AbstractMethodError at org.apache.spark.Logging$class.log(Logging.scala:50) at org.apache.spark.streaming.twitter.TwitterReceiver.log(TwitterInputDStream.scala:60) at org.apache.spark.Logging$class.logInfo(Logging.scala:58) at org.apache.spark.streaming.twitter.TwitterReceiver.logInfo(TwitterInputDStream.scala:60) at org.apache.spark.streaming.twitter.TwitterReceiver.onStart(TwitterInputDStream.scala:96) at org.apache.spark.streaming.receiver.ReceiverSupervisor.startReceiver(ReceiverSupervisor.s  ... View more

Please take a look at this thread for a response: http://community.cloudera.com/t5/Interactive-Short-cycle-SQL/Comma-delimited-string-to-individual-rows/m-p/41402#M1781 ... View more