You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/15 17:01:00 UTC
[jira] [Commented] (NIFI-6034) UI displays the wrong number of
"Running" processors
[ https://issues.apache.org/jira/browse/NIFI-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769504#comment-16769504 ]
ASF subversion and git services commented on NIFI-6034:
-------------------------------------------------------
Commit b508d6bfbc2b6a68fe2ab152de96611f06a8724a in nifi's branch refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b508d6b ]
NIFI-6033, NIFI-6034, NIFI-6035, NIFI-6036, NIFI-6037: Fixed bugs that were found during 1.9.0-RC1 validation. If multiple FlowFiles were written to same Content Claim, and a Processor attempted to read two of them wi within a single session, it would seek to the wrong part of the content or else throw a ContentNotFoundException. Updated logic for considering a processor to be 'running' / having 'active threads' if the processor is invalid upon NiFi restart but scheduled to run. Fixed NPE in FreeFormTextWriter. If MergeRecord reaches minimum number of records, flush writer after writing content out so that its minimum size can accurately be checked.
This closes #3309.
Signed-off-by: Bryan Bende <bb...@apache.org>
> UI displays the wrong number of "Running" processors
> ----------------------------------------------------
>
> Key: NIFI-6034
> URL: https://issues.apache.org/jira/browse/NIFI-6034
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
> Affects Versions: 1.9.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.9.0
>
>
> I chose to stop all Processors in my canvas. The UI still shows that 1 processor is running. If I go into the Process Group that shows 1 running processor, I can see that all processors are stopped or invalid.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)