[jira] [Updated] (NIFI-6822) When RunDuration > 0 ms, some statistics are not tracked correctly.

2020-01-06 Thread Mark Payne (Jira)


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

Mark Payne updated NIFI-6822:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> When RunDuration > 0 ms, some statistics are not tracked correctly.
> ---
>
> Key: NIFI-6822
> URL: https://issues.apache.org/jira/browse/NIFI-6822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> When using a Run Duration of more than 0 ms, the counts for the number of 
> FlowFiles & bytes in/out for connections is not tracked properly. 
> Additionally, the counter values that are presented are too low. This is due 
> to the counts that are maintained by the Process Session not being properly 
> updated. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (NIFI-6822) When RunDuration > 0 ms, some statistics are not tracked correctly.

2019-10-29 Thread Mark Payne (Jira)


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

Mark Payne updated NIFI-6822:
-
Fix Version/s: 1.11.0
   Status: Patch Available  (was: Open)

> When RunDuration > 0 ms, some statistics are not tracked correctly.
> ---
>
> Key: NIFI-6822
> URL: https://issues.apache.org/jira/browse/NIFI-6822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When using a Run Duration of more than 0 ms, the counts for the number of 
> FlowFiles & bytes in/out for connections is not tracked properly. 
> Additionally, the counter values that are presented are too low. This is due 
> to the counts that are maintained by the Process Session not being properly 
> updated. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)