@Michael Bronson The scenario is very well explained in the below article https://community.hortonworks.com/articles/16144/write-or-append-failures-in-very-small-clusters-un.html Are you seeing any datanode failures at the time of the issue? ... View more

@anurag The query failed because of the HDFS delegation token was not found in the cache and it has been cancelled by the running job. And the other job which has already started using that Delegation token, found that HDFS delegation token is already cancelled so the query failed with same error message. To resovlve this you need to add the property "tez.cancel.delegation.tokens.on.completion=false" Add in Custom tez-site via Ambari ... View more

This time the error is different GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7))] The exception means there is a mismatch between the key stored in the keytab and the key in the AD, please check the encryption type and also the Key Version Number (kvno) ... View more

This error states that NN is unable to determine the KDC server for kerberos authentication. Can you please validate your /etc/krb5.conf and that has got the realms pointing to your AD server? ... View more