<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Monitor Activity Issue in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Monitor-Activity-Issue/m-p/207043#M169004</link>
    <description>&lt;P&gt;It looks like the Threshold Duration is set to 1 minute in the configuration pictured. In that case, the processor started at 10:00 would trigger an inactivity message if the upstream processor had not generated a flowfile for the past 60 seconds. All flowfiles passed to the MonitorActivity processor will also be passed through to the Success relationship when the processor starts.&lt;/P&gt;&lt;P&gt;If instead the desired action is to send a dummy flowfile only if there has been no activity on the QueryDatabaseTable processor for one hour, scheduling both to run at 9:00 with a 60 minute threshold on the MonitorActivity should work.&lt;/P&gt;</description>
    <pubDate>Sat, 02 Jun 2018 07:38:02 GMT</pubDate>
    <dc:creator>wcbdata</dc:creator>
    <dc:date>2018-06-02T07:38:02Z</dc:date>
  </channel>
</rss>

