You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "jason (Jira)" <ji...@apache.org> on 2022/03/08 08:54:00 UTC
[jira] [Comment Edited] (NIFI-9767) PutKudu OutOfMemory Exception (GC overhead limit exceeded)
[ https://issues.apache.org/jira/browse/NIFI-9767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502803#comment-17502803 ]
jason edited comment on NIFI-9767 at 3/8/22, 8:53 AM:
------------------------------------------------------
The twenty pipeline test scenario is to reproduce the OOM error (-Xms4G、-Xmx4G)
In fact, found this issue because we have built some data pipelines including five putkudu processors(
-Xms12G、-Xmx12G). It is found that the heap cannot be free and the number of threads continues to increase until OOM(After 8 hours). After analysis, it is found that it is a problem with the putkudu processor. We are confused why the heap is not freed automatically and there are more and more threads
*Example:*
*Env. : -Xms4G、-Xmx4G*
*1.Create a data flow*
*2.Observe the heap status and threads after one hour*
!image-2022-03-08-15-43-46-091.png!
!image-2022-03-08-15-46-03-496.png|width=636,height=445!!image-2022-03-08-15-48-06-996.png|width=636,height=447!!image-2022-03-08-15-49-35-377.png|width=640,height=443!!image-2022-03-08-15-50-35-383.png|width=639,height=448!
*====================Result====================*
# *Heap is not freed and the memory grows and grows*
# *Thread increase in Kudu*
!image-2022-03-08-16-18-01-818.png!
!image-2022-03-08-16-18-38-261.png!
was (Author: JIRAUSER286229):
This test scenario is to reproduce the OOM error (-Xms4G、-Xmx4G)
In fact, found this issue because we have built some data pipelines including five putkudu processors(
-Xms12G、-Xmx12G). It is found that the heap cannot be free and the number of threads continues to increase until OOM(After 8 hours). After analysis, it is found that it is a problem with the putkudu processor. We are confused why the heap is not freed automatically and there are more and more threads
*Example:*
*Env. : -Xms4G、-Xmx4G*
*1.Create a data flow*
*2.Observe the heap status and threads after one hour*
!image-2022-03-08-15-43-46-091.png!
!image-2022-03-08-15-46-03-496.png|width=636,height=445!!image-2022-03-08-15-48-06-996.png|width=636,height=447!!image-2022-03-08-15-49-35-377.png|width=640,height=443!!image-2022-03-08-15-50-35-383.png|width=639,height=448!
*====================Result====================*
# *Heap is not freed and the memory grows and grows*
# *Thread increase in Kudu*
!image-2022-03-08-16-18-01-818.png!
!image-2022-03-08-16-18-38-261.png!
> PutKudu OutOfMemory Exception (GC overhead limit exceeded)
> ----------------------------------------------------------
>
> Key: NIFI-9767
> URL: https://issues.apache.org/jira/browse/NIFI-9767
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.15.0
> Environment: NiFi 1.15.0
> Reporter: jason
> Priority: Blocker
> Attachments: free_heap.png, image-2022-03-08-15-43-46-091.png, image-2022-03-08-15-46-03-496.png, image-2022-03-08-15-48-06-996.png, image-2022-03-08-15-49-35-377.png, image-2022-03-08-15-50-35-383.png, image-2022-03-08-16-18-01-818.png, image-2022-03-08-16-18-38-261.png, pipeline.png, total_threads.png
>
>
> PutKudu 1.15.0 eats up all the heap memory. Must restart NiFi to free heap.
> We create twenty the same of pipelines for test, will out of memory on few hours.Pipeline as shown in pipeline.png
--
This message was sent by Atlassian Jira
(v8.20.1#820001)