Hi Christopher,   It's done ! I hope this post can help other people !  ... View more

Hi ZhouJun,   Have you find a solution to your issue ?   I have the problem in my production and staging environnement since few months without any solutions. Network issue maybe ?   Thanks for your feedback ... View more

I made some changes just to try - added under /etc/hosts name node IP and server name - updated dns_lookup_kdc from true to false - udp_preference_limit from 0 to 1   No effect. It's still not working ... View more

For sur !   For your information because I haven't written : if I switch the default realm under krb5.conf from romulus to remus, romulus not working and remus is ok. it's like Nifi, when the default realm it's not the same as the principal realm is lost and try to use an another realm.   Further more, remus and romulus are not the true name and I need to change path, server name, ip and other objets to share with you 😉   Remus : Romulus : ... View more

Thanks for your anwser !   Waiting for several days to have an another Hadoop Cluster, it's now provided. After some configuration and check, it's working with some trouble. Let me explain my issue.   I have two Hadoop kerberized cluster : romulus and remus. For each one, kerberos configuration wad added in the krb5.conf Find an extract of this configuration :   [libdefaults] default_realm = romulus dns_lookup_realm = false dns_lookup_kdc = true rdns = false dns_canonicalize_hostname = false ticket_lifetime = 168h 0m 0s renew_lifetime = 90d forwardable = true udp_preference_limit = 0 ... [realms] romulus = { admin_server = <...> kdc = <...> } remus = { admin_server = <...> kdc = <...> }   If I use the kinit client , it's working fine.   I configure two GetHDFS processor, each one with the core-site.xml and hdfs-site.xml for Hadoop Configuration Resources, the keytab and the principal associated.   Case one : default_realm is romulus and I start the GetHDFS processor romulus. => Ok nice, I get the hdfs file (you can see the flowfile in the queue)   Case two: default_realm is still romulus and I start the GetHDFS processor remus => KO : Failed on local exception: java.io.IOException: Couldn't set up IO streams: java.lang.IllegalArgumentException: Server has invalid Kerberos principal: nn/<ip namenode active>@<ROMULUS>, expecting: nn/<ip namenode active>@<REMUS> Nifi trying to connect using the default realm romulus :    Server has invalid Kerberos principal: nn/<ip namenode active>@<ROMULUS>   And with the correct realm remus :   expecting: nn/<ip namenode active>@<REMUS>     To sum up : Nifi working well with the default realm but have an issue with the other realms.   Is there a configuation I missed ?   Thanks     ... View more

Hi,   Have you find a solution ? I have the same problem with my production cluster. HDFS HA is implemented from several years without problem.   But recently, we realized that a hdfs client have to wait 20 secondes when the server hosting the nn1 is shutdown. Exemple when I set the debug mode : 19/08/29 11:03:05 DEBUG ipc.Client: Connecting to XXXXX/XXXXX:8020 19/08/29 11:03:23 DEBUG ipc.Client: Failed to connect to server: XXXXX/XXXXX:8020: try once and fail. java.net.NoRouteToHostException: No route to host   Few informations :  Hadoop version : 2.7.3 dfs.client.retry.policy.enabled : false dfs.client.failover.sleep.max.millis : 15000 ipc.client.connect.timeout : 20000   Thanks for your help !    ... View more