Hi Minh, It is possible that the heap is being exhausted by EvaluateJsonPath if you are using it to add large JSON chunks as attributes. For example, if you’re creating an attribute from `$.` to put the entire JSON contents into attributes. Generally, attributes should be kept pretty small.
Otherwise, based on the flow described, the issue is almost certainly within the ExecuteGroovyScript. There, there’s not much guidance we can provide, as it’s running your own script. You’d need to understand what in your own script is using up all of the heap. Thanks -Mark On Nov 6, 2024, at 4:26 AM, [email protected] wrote: Hello all, We got a cluster with 10 nodes (4CPU/16Go) - NIFI 1.25 - jdk-11.0.19 We use this cluster to send the datas to GCP bucket, the datas are sent by others clusters, so we do S2S betweens them. I can't determine where is the issue. This message could by raise by EvaluateJsonPath/ExecuteGroovyScript/UpdateAttribute We have around 100.000 flowfiles (160Go datas) We need configure more than 1 tasks for each processor to run more faster but we have always this error - Caused by: java.io.IOException: Cannot update journal file /data/nifi/flowfile_repository/journals/130511810.journal because this journal has already encountered a failure when attempting to write to the file. If the repository is able to checkpoint, then this problem will resolve itself. However, if the repository is unable to be checkpointed (for example, due to being out of storage space or having too many open files), then this issue may require manual intervention. - Caused by: java.lang.OutOfMemoryError: Java heap space Could you give me some informations to find the root cause ? Thanks Minh
