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 2015/10/26 19:08:27 UTC

[jira] [Updated] (NIFI-1070) Add additional logging to FileSystemRepository to better understand how/when it is expiring archived data

     [ https://issues.apache.org/jira/browse/NIFI-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-1070:
-----------------------------
    Description: Currently, there is very little logging in the FileSystemRepository related to how and when it decides to expire data. It would be good to log at least at a debug level the amount of disk space available, the amount required for expiration, and when the task is running, in order to understand what is happening

> Add additional logging to FileSystemRepository to better understand how/when it is expiring archived data
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1070
>                 URL: https://issues.apache.org/jira/browse/NIFI-1070
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Minor
>             Fix For: 0.4.0
>
>
> Currently, there is very little logging in the FileSystemRepository related to how and when it decides to expire data. It would be good to log at least at a debug level the amount of disk space available, the amount required for expiration, and when the task is running, in order to understand what is happening



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