[jira] [Commented] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808760#comment-17808760 ] ASF subversion and git services commented on NIFI-12402: Commit 5d5f38b6e7f5b904f87a0ff8709f55c3408c68bf in nifi's branch refs/heads/support/nifi-1.x from nathluu [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5d5f38b6e7 ] NIFI-12402 Added Wait for Activity to MonitorActivity This closes #8063 Signed-off-by: David Handermann Co-authored-by: Vuong Nguyen Van Co-authored-by: nathluu (cherry picked from commit 6649115a34e302c5ebd45fd5c12e236357fc307f) > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.24.0 >Reporter: Tan Luu >Priority: Minor > Labels: patch-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808759#comment-17808759 ] ASF subversion and git services commented on NIFI-12402: Commit 6649115a34e302c5ebd45fd5c12e236357fc307f in nifi's branch refs/heads/main from nathluu [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6649115a34 ] NIFI-12402 Added Wait for Activity to MonitorActivity This closes #8063 Signed-off-by: David Handermann Co-authored-by: Vuong Nguyen Van Co-authored-by: nathluu > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.24.0 >Reporter: Tan Luu >Priority: Minor > Labels: patch-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799173#comment-17799173 ] Daniel Stieglitz commented on NIFI-12402: - [~nathluu] Change the statu above.s from 'Open' to 'Patch Available' by pressing 'Submit Patch' > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.23.2 >Reporter: Tan Luu >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798755#comment-17798755 ] Tan Luu commented on NIFI-12402: Yes, the expected behavior is to only trigger an inactive indicator after there was activity after the processor had been started then no activity for Threshold Duration. So the sequence of events is Start the processor -> activity comes -> no activity for "Threshold Duration" period In the pull request, I add a configuration property to toogle the processor behavior. It ensures backward compatibility > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.23.2 >Reporter: Tan Luu >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[
https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798628#comment-17798628
]
Daniel Stieglitz commented on NIFI-12402:
-
[~nathluu] In the above description
^The expected behavior is to only send an inactive indicator if there is
activity after the processor is started.^
Do you mean to say
The expected behavior is to only send an inactive indicator if there is
{color:#DE350B}no {color}activity after the processor is started.
?
> MonitorActivity generates inactivity indicator after it is started and
> threshold duration exceeds without actual activities
> ---
>
> Key: NIFI-12402
> URL: https://issues.apache.org/jira/browse/NIFI-12402
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Tan Luu
>Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Even though there is no activity, a start or restart of MonitorActivity
> processor produces an inactive flowfile after "Threshold Duration". This
> behavior creates a false positive notification cause there was no actual
> activity. The expected behavior is to only send an inactive indicator if
> there is activity after the processor is started.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[
https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798242#comment-17798242
]
Daniel Stieglitz commented on NIFI-12402:
-
[~nathluu] Can you please better describe your issue with the MonitorActivity
processor? It seems based on the description of 'Threshold Duration{*}'{*}
??Determines how much time must elapse before considering the flow to be
inactive??
that what you describe is the expected behavior.
> MonitorActivity generates inactivity indicator after it is started and
> threshold duration exceeds without actual activities
> ---
>
> Key: NIFI-12402
> URL: https://issues.apache.org/jira/browse/NIFI-12402
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.23.2
>Reporter: Tan Luu
>Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> MonitorActivity @OnScheduled method sets the "{*}inactive"{*} flag to false
> when it gets started so after the threshold duration without activity, an
> inactive indicator is created even if there is no actual activity.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
