https://community.cloudera.com/t5/Support-Questions/GSS-exception-error-seen-in-a-scenario-even-after-having/m-p/231197#M193041 <P>the machine names from the error log are the expected ones? So this basically means: env-2 is example1.com and example2.com is your hdfs master node (port 8020 should be hdfs file service from the name node)?</P><UL><LI>Are all the issues related to the communication between env-2 and your name node, or do you have other hosts involved as well? </LI><LI>does the process on env-1 start 5 times a day, or is it started once and continues to run (sleeping instead of terminating)?</LI><LI>the ticket renewal on env-1 is identical to the ticket renewal on env-2?</LI></UL><P>I am just wondering if it is possible, that your process on env-2 only takes the ticket at start-up, and when the ticket expires, it just doesn't pick the renewed ticket? If after a restart of your processes on env-2 all authentication issues are gone for the next around 20h, this might be the case. And if on env-1 the process is starting 5 times a day instead of continuously running it might be the reason that the issue is not occure on env-1. </P> Tue, 26 Dec 2017 19:29:05 GMT arald 2017-12-26T19:29:05Z