You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Matthew Clarke (JIRA)" <ji...@apache.org> on 2016/02/18 20:33:18 UTC

[jira] [Created] (NIFI-1536) multiple putHDFS processors can result in put failures.

Matthew Clarke created NIFI-1536:
------------------------------------

             Summary: multiple putHDFS processors can result in put failures.
                 Key: NIFI-1536
                 URL: https://issues.apache.org/jira/browse/NIFI-1536
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 0.5.0
         Environment: Java 1.8.0_60
OSX Yosemite 10.10.5
            Reporter: Matthew Clarke


When multiple putHDFS processors exist, the first to run loads some config that is then used by other putHDFS processors that are started. 

I have two dataflows setup.  One pushes data to a kerberized HDFS cluster while the other pushes data to a totally different non kerberized HDFS cluster.

Each putHDFS is configured to use its own core-sites.xml.  If I start the putHDFS that sends to the Kerberized HDFS cluster first, the other putHDFS will throw an error when it tries to send data to the non-kerberized HDFS cluster.
ERROR [Timer-Driven Process Thread-7] o.apache.nifi.processors.hadoop.PutHDFS
java.io.IOException: Failed on local exception: java.io.IOException: Server asks us to fall back to SIMPLE auth, but this client is configured to only allow secure connections.; Host Details : local host is: "<client hostname>/<client IP>"; destination host is: "<hdfs hostname>":<hdfs port>
....
Caused by: java.io.IOException: Server asks us to fall back to SIMPLE auth, but this client is configured to only allow secure connections.

Even if i stop the putHDFS that is sending to the kerberized HDFS and/or restart the putHDFS sending to the non kerberized HDFS, the above error persists.

I need to restart NiFi to clear condition.  After NiFi restart, if i run the putHDFS  that sends to the non-kerberized HDFS first, the putHDFS to the kerberized HDFS will still work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)