[jira] [Commented] (NIFI-1270) When a session is rolled back, the Tasks/Time shown on Processors should be updated

["Mark Payne (JIRA)" <ji...@apache.org>]

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

Mark Payne commented on NIFI-1270:
----------------------------------

Looking through the code, I couldn't see how this was possible. I created a template to verify, and sure enough the tasks/time are indeed updated. I believe someone else had mentioned this issue to me, but I cannot replicate it. With the attached template, we generate flowfiles 1 per second, and then have DistributeLoad choose a destination for it. Once the connection with the '1' relationship is full (3 FlowFiles), the DistributeLoad processor will continue to run but will roll back because the configured distribution strategy requires that all relationships be available. When this happens, the Tasks/Time are still updated.

I will close this ticket for now, since I reported it and can not replicate the issue. If the problem is encountered again, we can re-investigate, as there may be some edge condition that I am missing perhaps.

> When a session is rolled back, the Tasks/Time shown on Processors should be updated
> -----------------------------------------------------------------------------------
>
>                 Key: NIFI-1270
>                 URL: https://issues.apache.org/jira/browse/NIFI-1270
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>         Attachments: rollback-increments-counts-and-time.xml
>
>
> Currently, if a Processor runs and then rolls back the session, we update the bytes read / bytes written counts for the Processor but not the tasks/time. We should update the tasks/time as well. We should not, however, update the flowfiles/bytes in, as that would cause a lot of confusion (implying e.g., that many came in and only 1 went out).



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