@sayak17  so this looks doable as I described above.  Not sure what program you are using in your screenshots as it does not show the full rest-api call structure. But your process would be as as follows: 1. Get bearer token 2. Extract bearer token from response body and place in FlowFile attribute 3. Format flowfile attribute as needed for use by the rest of the api-calls 4. Using bearer token make get request to the ../sites rest-api endpoint 5. Use ExtractText to extract the site id to a new FlowFile Attribute 6. Use bearer token again and use NiFi Expression Language to dynamically create the rest-api url to include the site id. 7. From response, extract the Drive id to another new FlowFile Attribute as above. 8. Use bearer token again and use NiFi Expression Language to dynamically create the rest-api url to include the drive id. 9 finally do whatever you need to do with the response json you get from that final rest-api call. Matt ... View more

@Meeran  Sharing the full exception that was output when you tried to import key maybe helpful, But I am also not sure why you are trying to add a Client private key to your AWS load-balancer? I am not well versed on AWS load balancer configuration, so helping you get past your LB setup/configuration issue may be difficult for me.  I do know TLS very well and explained the meaning of the two TLS exceptions you encountered.    The HTTPS LB exception could be resolved by making sure the TrustedCertEntry(s) for the complete trust chain for the HTTPS LB's privateKey are present in the NiFi-Registry's truststore.jks.  You should also add the trustedcertEntry for the NiFi CA you appeared to be using to the truststore used by your HTTPS LB. Thank you, Matt ... View more

@Drozu, Have any of the replies 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.   ... View more

Hello Matt, Thank you ! this solved the error (now I'm facing another one, but will figure it out 🙂 ). For further reference I had to configure those 3 lines in nifi.properties : nifi.security.identity.mapping.pattern.dn=^CN=(.*?), OU=(.*?) nifi.security.identity.mapping.transform.dn=NONE nifi.security.identity.mapping.value.dn=$1@$2   Thanks. Vince. ... View more

Thanks Mr @MattWho . In addition to your solution, i looked into Network Attached Storage & NFS. So i configured nfs server on the source, then configured nfs client on the destination. And lastly mount the source folder to the destination folder on restart. Thank you all. ... View more

How does the backpressure apply to nodes in a cluster? If the threshold is 10 000 object does that mean that the queue in total cannot reach 10 000 objects or does it apply to each node individually?   Also the same question for the ControlRate processor, does it rate limit based on the node statistics or the total stats across the cluster? ... View more

How does the backpressure apply to nodes in a cluster? If the threshold is 10 000 object does that mean that the queue in total cannot reach 10 000 objects or does it apply to each node individually?   Also the same question for the ControlRate processor, does it rate limit based on the node statistics or the total stats across the cluster? ... View more

Hi @SAMSAL ,   thank you for your help, but you're absoluty right in your second post - the first one seems very "uncomfortable".   @MattWho: I really don't care about the content, i've created backup-files in the stages before mailing and only the consumed filenames are relevant for mail. Last time there was 350 files and 35MB for backup 😉 ... View more

I know.Need FQDN likes testhost.magg.com,Thanks   ... View more

@Luwi  An "active content claim" would be any content claim where a FlowFile exist still referencing bytes of content in that claim.  A NiFi content claim file can contain the content for 1 too many FlowFiles.  So all it takes is one small FlowFile still queued in some connection anywhere on your NiFi canvas to prevent a content claim from being eligible to be moved to archive.  This is why the total reported content queued on yoru canvas will never match the disk usage in your content_repository. This article is useful in understanding this process more: https://community.cloudera.com/t5/Community-Articles/Understanding-how-NiFi-s-Content-Repository-Archiving-works/ta-p/249418 Thank you, Matt ... View more