You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Michael Moser (JIRA)" <ji...@apache.org> on 2017/03/13 20:25:43 UTC
[jira] [Assigned] (NIFI-2481) FileSystemRepository: maxArchiveBytes
calculated incorrectly
[ https://issues.apache.org/jira/browse/NIFI-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Moser reassigned NIFI-2481:
-----------------------------------
Assignee: Michael Moser
> FileSystemRepository: maxArchiveBytes calculated incorrectly
> ------------------------------------------------------------
>
> Key: NIFI-2481
> URL: https://issues.apache.org/jira/browse/NIFI-2481
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Brandon DeVries
> Assignee: Michael Moser
> Priority: Minor
>
> It appears as though the calculation of maxArchiveBytes in FileSystemRepository.java might be backwards. The line in question\[1\] is:
> {code}
> final long maxArchiveBytes = (long) (capacity * (1D - (maxArchiveRatio - 0.02)));
> {code}
> if you say capacity = 1000, then you get the following:
> maxArchiveRatio = .1 ==> maxArchiveBytes = 920
> maxArchiveRatio = .5 ==> maxArchiveBytes = 520
> maxArchiveRatio = .9 ==> maxArchiveBytes = 120
> In other words, as you increase the nifi.content.repository.archive.max.usage.percentage, you would be decreasing the bytes allowed for archiving...
> \[1\] https://github.com/apache/nifi/blob/rel/nifi-0.7.0/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/FileSystemRepository.java#L189
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)