[
https://issues.apache.org/jira/browse/NIFI-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118061#comment-15118061
]
ASF GitHub Bot commented on NIFI-1200:
--------------------------------------
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/191
NIFI-1200 fixed CPU saturation in FileSystemRepository
added minimal interval
added WARN message if set interval is lower
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1200
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/191.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #191
----
commit 795d498b04dc2f86ef4ffdd14c91be282953058f
Author: Oleg Zhurakousky <[email protected]>
Date: 2016-01-26T21:21:31Z
NIFI-1200 fixed CPU saturation in FileSystemRepository
added minimal interval
added WARN message if set interval is lower
----
> 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
> Assignee: Oleg Zhurakousky
> Priority: Minor
> Fix For: 0.5.0
>
>
> Was reported in the dev thread by [email protected]
> 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)
