You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/03/09 23:08:40 UTC

[jira] [Commented] (NIFI-1315) Content Repository appears to not apply strict enough backpressure

    [ https://issues.apache.org/jira/browse/NIFI-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188146#comment-15188146 ] 

Mark Payne commented on NIFI-1315:
----------------------------------

I don't think this one will make it into 060 either. It will take a significant amount of time to investigate and find a root cause, and 0.6.0 is approaching quickly.

> Content Repository appears to not apply strict enough backpressure
> ------------------------------------------------------------------
>
>                 Key: NIFI-1315
>                 URL: https://issues.apache.org/jira/browse/NIFI-1315
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.4.0
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 0.6.0
>
>
> I was able to setup a dataflow running at a high rate, with CPU load average about double the number of CPUs. With the content repository configured to archive to the point of 80% disk utilization, I still eventually ran out of disk space. NiFi did handle it properly, rolling back sessions and retrying until the disk space was reclaimed from the archive, but it appears that our archive does not apply tight enough constraints for this backpressure, as it should never have gotten to the point of being out of disk space.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)