Don't know the exact cause that it was not working even i restarted the Yarn, when i had another chance to restart the Yarn, the issue was resolved. ... View more

So, summarizing: When starting Spark with --deploy-mode client one must distribute Jaas file and keytab to every machine. When starting Spark with --deploy-mode cluster one must distribute Jaas file and keytab with --files and/or --keytab. ... View more

After adding the "classpath" when I execute,    hadoop classpath, it doesn't return the path that I have added.   Any ideas? ... View more

Ok @mbigelow thanks. I also reasearched more and found this hortonworks link, https://community.hortonworks.com/questions/45962/dataxceiver-error-processing-write-block-operation.html where they say we can ignore this error.  This issue has been already fixed in 2.3 version of ambari but of course I am using CDH.   Thanks, Shilpa ... View more

Hi ,   Idle session works indeed . I have set it to 1 hour but can not wait 1 hour untill killed queries will be dead .   Work arround that I found is disconnecting from the session after query has been cancelled in the UI .   It should work better .   Thanks   Alon ... View more

@mbigelow Thank you, that solved the issue. The /opt/cloudera/csd dir was empty, I downloaded CSD and configured it and then re-added service. The above exception is resolved. ... View more

I am going to repost this as an HBASE SNAPSHOT question. ... View more

I've explored idle query timeout and idle session out before itself and using in prod cluster as well. Those timeouts are not related to idle connections. Idle session timeout is taking care of only session, but still connection is established and being counted under active connections in use. On reading about SocketTimeout option in jdbc driver, it clearly said it will take care of idle connections. Hence tried it out, but doesn't seem to work. Most of users here, using sql workbench through jdbc driver keeps opening new tab for every new query and don't close their tab for the whole day. I assumed sockettimeout will solve this problem. ... View more