I believe MergeContent Merging Strategy is set to Defragment ? If it is set to Defragment then MergeContent will wait to receive all flow file part of fragment.count. so what happened to the remaining 2 flow files? which relationships they move? failure?  and terminated on Processor itself assuming as per screenshot . If you wish to merge with reamaning 8 then Merging Strategy needs to be changed but that could be lead to case where all 8 records can not be merged together all the time since there is no correlation, or if you just want to merge all records irrespective of failure or success , then you need to have failure or success both relationships configured for MergeContent .   Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

With LB in place, you are reaching NiFi as anonymous when LB has not been configured to pass the user identity to NiFi that what I understand from looking the log snippet.. Please refer this page to check if proxy details are configured correctly  https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration ... View more

Have you tested ListenFTP without setting SSLContextService? just to make sure supplied username and password is correct?   ... View more

It seems you misunderstood the usage of UpdateCounter, UpdateCounter is only used for debugging purposes, when you use UpdateCounter in flow then counter option at NiFi--Humburgenr Menu will give you the counter details.. you can not reuse or call these details on any other processor.      ... View more

There are two aspects of your question "How do you configure a PutMongo NiFi Processor "   1. Connection details:   Connection URL, User Auth, Wire encryption (SSL ) 2. Actual Query: make sure query syntax is correct.   If you can post an error snipped and snap from the processor config to be able to isolate if this query issue or connection issue. Assume if this is with query-related issue , then you can verify if the same query works from the generic mongo db client? if not then same query will not work from nifi:PutMongo as well.    Thank You.       ... View more

NiFi  as a service alone can not autoscale irrespective of the type public/private cloud provided until it is customized and managed by different automation and scaling applications over the public cloud.   But Cloudera offers NiFi as Data flow Expreinace in the public cloud which does support autoscaling Please check https://docs.cloudera.com/dataflow/cloud/release-notes/topics/cdf-whats-new.html for more info.   Thank You. ... View more

also, you mentioned "Processor doesn't read saved attribute" Which specific processor you are complaining about ?  ... View more

trying to understand your flow pipeline with respect to your use case explanations, You have two upstream queued for InvokeHTTP , in one  using ExtractText you are extracting text , which will be stored in flow file as an attribute then running HTTP Method from InvokeHTTP and configured Attributes to Send for the attributed which is created by ExtractText ?  What GenreateFlowFile os doing in this flow?  what evaluation is configured with EvaluateJsonPath ? Please provide more details   ... View more

javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_required    is very generic error for SSL and can cause due to multiple factors such as    1. TLS version mismatch -->TLS version can be changed with StandardSSLContextService  2. Incompatible cipher suites in use by the client and the server --> This can be due to Java version in use by NiFi and Active MQ server  and can be checked if there are any specific  cipher is set at Active MQ   following file needs  to be reviewed   jre/lib/security/java.security             3. How client certificate obtained and imported in truststore file which is configured under   StandardSSLContextService--> You can use SSLPoke to verify connectivity outside of NiFi using same truststore file to makesure if the certificate is fine.     Thank you.        ... View more