@AlokKumar  There are a lot of steps involved with setting up a NiFi cluster.  Without knowing the details of your standalone NiFi configuration, giving specific guidance on what it would take to convert your standalone to a cluster would be challenging and lengthy.  I'd recommend reading through the https://nifi.apache.org/nifi-docs/administration-guide.html and setting up a separate NiFi cluster to understand all the configurations that need to be made to be successful before implementing this on your production env.  https://nifi.apache.org/nifi-docs/administration-guide.html#clustering  https://nifi.apache.org/nifi-docs/administration-guide.html#basic-cluster-setup Basic requirements: 1. NiFi cluster requires Zookeeper (ZK): min 3 ZK nodes..  ZK must have quorum to work correctly.  ZK is utilize to facilitate election of NiFi cluster node roles cluster coordinator node (handle request replication to all nodes in NiFi cluster) and Primary node (only node that will schedule "primary node" only configured canvas components).  NiFi offers the ability to start an embedded ZK, but keep in mind that if NiFi is stopped on a node it also stops that NiFi's ZK.  ZK is also used to store shared cluster state for processors that need to share state across all nodes.  https://nifi.apache.org/nifi-docs/administration-guide.html#embedded_zookeeper 2. You'll need to configure all NiFi nodes the same (configuration files should match except node specific values).  3. You'll want to use a more robust configurable authorizer which means also using some form of user authentication besides default single-user enabled out-of-the-box for standalone NiFi evaluation.   ldap-provider, kerberos-provider, or SSL certificates are most commonly used, but other options can be found in admin guide as well. https://nifi.apache.org/nifi-docs/administration-guide.html#user_authentication https://nifi.apache.org/nifi-docs/administration-guide.html#multi-tenant-authorization https://nifi.apache.org/nifi-docs/administration-guide.html#config-users-access-policies Hope this help get you started on your clustered NiFi journey. I encourage you to create more community questions as you explore this option should you run into complications. Thanks, Matt   ... View more

@MarinaM, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution to help others find the answer more easily in the future.  ... View more

I wanted to add that when using the IP address:104.36.197.137 of sftp.uber.com it worked with NiFi 2.9.0 using PROXY HTTP Configuration service.   It has nothing to do with the OS DNS resolution because it is connected to the proxy server to resolve the destination. When using sftp.uber.com, NiFi PROXY HTTP configuration service, it never reached the proxy server at all from the Proxy trace debug.  It has to be a NiFi PROXY configuration resolution with hostname when it works with 1.2x and not 2.x. ... View more

Thanks, I will digest and talk to the nifi builders about this. ... View more

@nisaar  I agree with @vafs  that sharing the completed ERROR and stack trace is always gong to be most helpful in your community questions.  Those full stack traces will have classes like "net.schmizz.sshj.transport" that you could try putting in to DEBUG within the NiFi logback to see what additional logging that class (not a NiFi library, but used by NiFi) may provide.  Matt ... View more

Thank you. Setting the load balancer timeout to 25seconds worked for me with NiFi 2.8 ... View more

@AlokKumar Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

@fnimi Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

@oka  Perhaps others in the community may hav additional suggestions here, but since the "-" is not a valid character in JMS, you would need to use a AMQP processor to support these headers. As mentioned before there is a https://issues.apache.org/jira/browse/NIFI-14670 jira for adding AMQP 1.0 support to ConsumeAMQP processor, but it is still open and unassigned. Now that jira points to using the Qpid JMS Client in ConsumeJMS and as you experienced it works but still has limitations.  Those limitations impact these specific properties with the "-" in the name.  I would suggest adding your experience with trying to use Qpid AMQP in the above jira and what impacts it has on the two headers you require to maybe push the Apache community to adding AMQP 1.0 support to the AMQP specific processors. Additionally, there is this jira (https://issues.apache.org/jira/browse/QPID-4992), where an individual expressed some success preserving the content type header by using ActiveMQ JMS API instead of the Qpid AMQP JMS API.  So you may want to give this jira a read and maybe try this for yourself.  Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt   ... View more