These items could also help.   - Check the jobs that are running during the time of incident. You can also check via CLI in the master node using the command below and observe what are the jobs running.    $ yarn top - If yes, reduce the job running meaning you can do a job scheduling to manage the jobs running on a specific time. - Another thing, if the cluster unable to manage your jobs you'll need to expand the cluster to have better performance.   Thanks.     ... View more

If you have a support contract with Cloudera, you can contact us via details at the following link under ‘How can I contact support?’ and we will be happy to assist: https://my.cloudera.com/faq.html#support If you do not yet have a support contract with Cloudera, you would need to first speak with a sales representative in order to contract with support via the following link: https://www.cloudera.com/contact-sales.html ... View more

You are welcome.   The query was cancelled due to some exception but there are no details of the exception in your query info. You can download the text query profile from CM. If you still can't see the detail in the query profile, you need to grep the query id 3348f74b129b0dae:1666447600000000 from the impala INFO log files on p1i-hdp-srv11.lnt.com. You should be able to see which query instance hit the exception. Then you can grep the instance id from the impala INFO log files on the host where the instance was running to look for the cause. ... View more