jsanko9

Not sure if helpful at all but if I change: dfs.namenode.kerberos.principal hdfs/[email protected] to "host/{{actual hostname}}@REGION.COMPANY.COM" I get: > Couldn't connect to namenode: no available namenodes: SASL handshake: wrong Token ID....

This is something I'm also interested in, and would be very helpful. Tool I'm using is running on version 2 minimum, soon to be upgraded to 5 I hear. But...