[
https://issues.apache.org/jira/browse/NIFI-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated NIFI-6124:
------------------------------
Description:
NiFi HDFS processors appear to be resolving the host component of the kerberos
principal given an hdfs-site.xml using the usual Hadoop _HOST placeholder like
so:
{code:java}
<property>
<name>dfs.namenode.kerberos.principal</name>
<value>hdfs/_HOST@<domain></value>
</property>{code}
This sort of configuration works across the Hadoop ecosystem but not in NiFi it
seems where it results in an exception like this:
{code:java}
2019-03-15 09:55:42,556 INFO [Timer-Driven Process Thread-6]
o.a.h.io.retry.RetryInvocationHandler java.io.IOException: Failed on local
exception: java.io.IOException: Couldn't set up IO streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
hdfs/<fqdn>@<domain>, expecting: hdfs/<ip_x.x.x.x>@<domain>; Host Details :
local host is: "<fqdn>/<ip_x.x.x.x>"; destination host is: "<ip_x.x.x.x>":8020;
, while invoking ClientNamenodeProtocolTranslatorPB.getFileInfo over
<ip_x.x.x.x>/<ip_x.x.x.x>:8020 after 9 failover attempts. Trying to failover
after sleeping for 17661ms.
{code}
was:
NiFi HDFS processors appear to be resolving the host component of the kerberos
principal given an hdfs-site.xml using the usual Hadoop _HOST placeholder like
so:
{code:java}
<property>
<name>dfs.namenode.kerberos.principal</name>
<value>hdfs/_HOST@<domain></value>
</property>{code}
Results in an exception like this:
{code:java}
2019-03-15 09:55:42,556 INFO [Timer-Driven Process Thread-6]
o.a.h.io.retry.RetryInvocationHandler java.io.IOException: Failed on local
exception: java.io.IOException: Couldn't set up IO streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
hdfs/<fqdn>@<domain>, expecting: hdfs/<ip_x.x.x.x>@<domain>; Host Details :
local host is: "<fqdn>/<ip_x.x.x.x>"; destination host is: "<ip_x.x.x.x>":8020;
, while invoking ClientNamenodeProtocolTranslatorPB.getFileInfo over
<ip_x.x.x.x>/<ip_x.x.x.x>:8020 after 9 failover attempts. Trying to failover
after sleeping for 17661ms.
{code}
> NiFi HDFS processors resolve Kerberos principal _HOST component to an IP
> address and get wrong principal error - Server has invalid Kerberos
> principal: ...host..., expecting: ...ip...
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6124
> URL: https://issues.apache.org/jira/browse/NIFI-6124
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Hari Sekhon
> Priority: Major
>
> NiFi HDFS processors appear to be resolving the host component of the
> kerberos principal given an hdfs-site.xml using the usual Hadoop _HOST
> placeholder like so:
> {code:java}
> <property>
> <name>dfs.namenode.kerberos.principal</name>
> <value>hdfs/_HOST@<domain></value>
> </property>{code}
> This sort of configuration works across the Hadoop ecosystem but not in NiFi
> it seems where it results in an exception like this:
> {code:java}
> 2019-03-15 09:55:42,556 INFO [Timer-Driven Process Thread-6]
> o.a.h.io.retry.RetryInvocationHandler java.io.IOException: Failed on local
> exception: java.io.IOException: Couldn't set up IO streams:
> java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
> hdfs/<fqdn>@<domain>, expecting: hdfs/<ip_x.x.x.x>@<domain>; Host Details :
> local host is: "<fqdn>/<ip_x.x.x.x>"; destination host is:
> "<ip_x.x.x.x>":8020; , while invoking
> ClientNamenodeProtocolTranslatorPB.getFileInfo over
> <ip_x.x.x.x>/<ip_x.x.x.x>:8020 after 9 failover attempts. Trying to failover
> after sleeping for 17661ms.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
