Member since
03-26-2020
3
Posts
0
Kudos Received
0
Solutions
08-14-2020
05:51 AM
1 Kudo
@NY There are several bugs related content repository failing to clean-up under specific conditions. Based on your description and version of HDF, the most likely bugs are the following: https://issues.apache.org/jira/browse/NIFI-6846 https://issues.apache.org/jira/browse/NIFI-5771 Both of the above would result in cleanup occurring only on NiFi Restart once the condition occurs. If you are using the VolatileFlowFileRepository implementation which is uncommon, you may be hitting: https://issues.apache.org/jira/browse/NIFI-6236 While you are not hitting below jira because it was only introduced in Apache NIFi 1.9.1 (HDF3.4.0 - removed) and fixed in HDF 3.4.1, sharing for completeness here: https://issues.apache.org/jira/browse/NIFI-6150 All the above are addressed, except NIFI-6846 are addressed in HDF 3.4.1 (Apache NiFi 1.9.2). All above are fixed in HDF 3.5.1 (Apache NiFi 1.11.4). I recommend upgrading to HDF 3.5.x (latest) Hope this helps, Matt
... View more
03-27-2020
01:20 PM
@NY Anything you can do via the NiFi canvas, you can also accomplish via the rest-api. So you can create a queue listing via a rest-api call: curl http://<nifi-hostname>:<port>/nifi-api/flowfile-queues/<connection-uuid>/listing-requests The above call will return a response that includes the URL you need to use to retrieve those results. for example: http://<nifi-hostname>:<port>/nifi-api/flowfile-queues/<connection-uuid>/listing-requests/1d98d557-0171-1000-ffff-ffffd559ca47 Then query for the listings results curl http://<nifi-hostname>:<port>/nifi-api/flowfile-queues/<connection-uuid>/listing-requests/1d98d557-0171-1000-ffff-ffffd559ca47 This return a json with all the FlowFiles from that specific connection queue from all nodes in your NiFi cluster. That json would need to be parsed for info like nodes where the "lineageDuration" epoch time is x amount of time older then now, the "clusterNodeAddress" (which node holds the file), and maybe filename". and then delete the queue listing when done. (this is important or it stays around using heap space). curl -X DELETE http://<nifi-hostname>:<port>/nifi-api/flowfile-queues/<connection-uuid>/listing-requests/1d98d557-0171-1000-ffff-ffffd559ca47 Hope this helps, Matt
... View more