You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Adam Lamar (JIRA)" <ji...@apache.org> on 2015/11/19 21:48:11 UTC
[jira] [Commented] (NIFI-1200) FileSystemRepository saturates CPU
when archive directories are empty
[ https://issues.apache.org/jira/browse/NIFI-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014320#comment-15014320 ]
Adam Lamar commented on NIFI-1200:
----------------------------------
[~ozhurakousky] Thanks for filing this issue! Please note that this issue was much worse when running on OpenJDK. CPU usage held around 20-30% without the sleep, but the Oracle JDK wasn't nearly as busy.
> FileSystemRepository saturates CPU when archive directories are empty
> ---------------------------------------------------------------------
>
> Key: NIFI-1200
> URL: https://issues.apache.org/jira/browse/NIFI-1200
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Oleg Zhurakousky
> Priority: Minor
> Fix For: 0.5.0
>
>
> Was reported in the dev thread by adamonduty@gmail.com
> The piece of code responsible is
> {code}
> for (int i = 0; i < SECTIONS_PER_CONTAINER; i++) {
> . . .
> if (!Files.exists(archive)) {
> continue;
> }
> . . .
> }
> {code}
> . . where continue happens without any delay.
> It was also confirmed by Adam that small Thread.slleep(..) takes care of the problem. What puzzles me is that the loop itself has a finite end so, need to look how the parent operation is invoked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)