<?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: NiFi: Flowfile retries in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/297335#M45793</link>
    <description>&lt;P&gt;Hi umair,&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/50133"&gt;@umair_ahmed&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35453"&gt;@Wynner&lt;/a&gt;&amp;nbsp;,&amp;nbsp;@&lt;A href="https://community.cloudera.com/users/525/mclark.html" rel="user" target="_blank"&gt;Matt Clarke&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The retry mechanism of the unmatched records from the invoke HTTP which was very helpful. Could you please more elaborate information on the advanced settings of the Update attribute. And the Route attribute and Execute stream command.&lt;/P&gt;&lt;P&gt;1) 5 times it needs to retry but only four times it has been mentioned in advanced property of the update attribute. And the expression on the advanced setting of the update attribute needs to be :&amp;nbsp;${retry.counter:replaceNull('0'):equals('1')} whether it needs to be in the incremented fashion like&amp;nbsp;&lt;/P&gt;&lt;P&gt;sleeponeminute -&amp;gt;&amp;nbsp;${retry.counter:replaceNull('0'):equals('1')}&lt;/P&gt;&lt;P&gt;sleepthirtyminute -&amp;gt;&amp;nbsp; ${retry.counter:replaceNull('0'):equals('2')}&lt;/P&gt;&lt;P&gt;sleeponehour -&amp;gt;&amp;nbsp; ${retry.counter:replaceNull('0'):equals('3')}&lt;/P&gt;&lt;P&gt;sleeptwohours -&amp;gt;&amp;nbsp; ${retry.counter:replaceNull('0'):equals('4')}&lt;/P&gt;&lt;P&gt;sleepmaxcount -&amp;gt;&amp;nbsp;${retry.counter:replaceNull('0'):equals('5')} (i.e., the sleeptime for the sleepmaxcount rule set to 180m)&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) For the RouteOnAttribute, I have set the 5 conditions as per your screenshot. I can see the flowfile between the connector updateattribute and RouteOnAttribute then i couldn't see the flowfile in the next connector.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please elaborate more on the property setting of the other two processors Routeon Attribute and Execute StreamCommand(CommandPrompt property: It states take the environmental value ). Working Directory and Output destination attribute could you please explain these properties as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance,&lt;/P&gt;&lt;P&gt;Karthick&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 04 Jun 2020 07:21:41 GMT</pubDate>
    <dc:creator>Karthick93</dc:creator>
    <dc:date>2020-06-04T07:21:41Z</dc:date>
    <item>
      <title>NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171724#M45781</link>
      <description>&lt;P&gt;For e.g. PutHDFS processor, if the failure relationship is connected to itself&lt;/P&gt;&lt;P&gt;1) How to control the number of retries of a single flowfile? &lt;/P&gt;&lt;P&gt;2) I see "FlowFile Expiration" can be used to expire the message (meaning discard the Flowfile content if it cannot be reprocessed within a specified period of time).  Is there a way to retain the FlowFile content after specified number of retries, that is to persist on a different channel say local file system (PutFile) and perhaps be able to send email notification ? &lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2016 13:18:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171724#M45781</guid>
      <dc:creator>ashsskum</dc:creator>
      <dc:date>2016-11-10T13:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171725#M45782</link>
      <description>&lt;P&gt;
	I am not aware of a setting to specify a number of retry attempts. If you think this would be a common requirement, please &lt;A target="_blank" href="https://issues.apache.org/jira/secure/CreateIssue!default.jspa"&gt;file a Jira&lt;/A&gt; requesting the feature for Apache NiFi. You can route data through a series of processors a specified number of times using a loop as &lt;A target="_blank" href="https://gist.github.com/ijokarumawak/01c4fd2d9291d3e74ec424a581659ca8"&gt;demonstrated by Koji Kawamura here&lt;/A&gt;. You can also pair an &lt;CODE&gt;UpdateAttribute&lt;/CODE&gt; processor with your &lt;CODE&gt;PutHDFS&lt;/CODE&gt; so when following the failure relationship, an attribute is added/updated indicating the number of failed tries. You can then route continually-failed data to your fallback flow (&lt;CODE&gt;PutFile&lt;/CODE&gt; &amp;amp; &lt;CODE&gt;PutEmail&lt;/CODE&gt;, etc.). &lt;/P&gt;&lt;P&gt;
	Flowfile expiration refers to the age (amount of time since the flowfile entered NiFi) before the flowfile should be dropped, so it is not an ideal fit for this use case.  &lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2016 13:44:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171725#M45782</guid>
      <dc:creator>alopresto</dc:creator>
      <dc:date>2016-11-10T13:44:45Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171726#M45783</link>
      <description>&lt;P&gt;@kumar&lt;/P&gt;&lt;P&gt;Check out this template as it will do exactly what you are looking for:&lt;/P&gt;&lt;P&gt;&lt;A href="https://cwiki.apache.org/confluence/download/attachments/57904847/Retry_Count_Loop.xml?version=1&amp;amp;modificationDate=1433271239000&amp;amp;api=v2"&gt;Retry_Count_Loop.xml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Just feed your failure relationship in to this process group and the output from this process group back to your processor.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2016 21:01:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171726#M45783</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2016-11-10T21:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171727#M45784</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/525/mclark.html" nodeid="525"&gt;@Matt Clarke&lt;/A&gt; &lt;/P&gt;&lt;P&gt;hi using invoke HTTP  and  retry relationship is connected to itself and i want to control reties up to some count and on time that is it retry at certain time .at the same time i want to limit reties up to 5 counts..&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 13:27:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171727#M45784</guid>
      <dc:creator>umair_ahmed</dc:creator>
      <dc:date>2017-05-08T13:27:58Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171728#M45785</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/18135/umairahmed.html" nodeid="18135"&gt;@umair ahmed&lt;/A&gt; &lt;/P&gt;&lt;P&gt;The Retry loop template above allows you to configure the number of retry attempts before existing the loop.  I am not sure what you mean by "on time that is it retry at certain time".  If the intent is to slow how fast the FlowFile is retired, you could add an additional routeOnAttribute processor to the failure loop to to loop until file has aged x amount of time.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 20:00:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171728#M45785</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2017-05-08T20:00:47Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171729#M45786</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/525/mclark.html" nodeid="525"&gt;@Matt Clarke&lt;/A&gt;
&lt;/P&gt;&lt;P&gt;thanks for fast replying &lt;/P&gt;&lt;P&gt;"on time that is it retry at certain time .at the same time i want to limit reties up to 5 counts.." i mean  i want do combination of count and time for limiting retries&lt;/P&gt;&lt;P&gt;means...that&lt;/P&gt;&lt;P&gt;first retry  after 1 min &lt;/P&gt;&lt;P&gt;second after 30 min vice versa &lt;/P&gt;&lt;P&gt;limiting retry up to 5 count &lt;/P&gt;&lt;P&gt;thanks &lt;/P&gt;&lt;P&gt;umair&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 20:23:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171729#M45786</guid>
      <dc:creator>umair_ahmed</dc:creator>
      <dc:date>2017-05-08T20:23:03Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171730#M45787</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/18135/umairahmed.html" nodeid="18135"&gt;@umair ahmed&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Just spoke with Dave and he cleaned up his template/response to you here:
&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/questions/101496/nifi-invokehttp-retries.html#answer-101588"&gt;https://community.hortonworks.com/questions/101496/nifi-invokehttp-retries.html#answer-101588&lt;/A&gt;&lt;/P&gt;&lt;P&gt;His solution for triggering sleep based on retry count set in my template is perfect for meeting your needs. It also scales very easily by simply adding additional timer rules to the advanced UI of the UpdateAttribute processor.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 21:13:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171730#M45787</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2017-05-08T21:13:40Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171731#M45788</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/525/mclark.html" nodeid="525"&gt;@Matt Clarke&lt;/A&gt; &lt;/P&gt;&lt;P&gt;In ExecuteStreamCommand processor command path= ' usr/bin/sleep' what is this thing because i am getting exception in ExecuteStreamCommand processor .."The System cannot find the file specified" what is this file &lt;/P&gt;&lt;P&gt;i am not getting it &lt;/P&gt;&lt;P&gt;and i am using windows&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;umair&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 13:37:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171731#M45788</guid>
      <dc:creator>umair_ahmed</dc:creator>
      <dc:date>2017-05-09T13:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171732#M45789</link>
      <description>&lt;P&gt;The "sleep" command is a linux command.  The command simply runs and waits the configured amount of time before exiting.  Typically this command in linux is found under /usr/bin/sleep.  I noticed above is missing the leading "/" .  But if it is still not found, try searching your linux for it.  It is installed as part of the linux "coreutils" rpm.&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 19:41:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171732#M45789</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2017-05-09T19:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171733#M45790</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/525/mclark.html" nodeid="525"&gt;@Matt Clarke&lt;/A&gt; &lt;/P&gt;&lt;P&gt;ok what is alternative command for windows .i already tried timeout and waitfor but both not work for me &lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 12:03:16 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171733#M45790</guid>
      <dc:creator>umair_ahmed</dc:creator>
      <dc:date>2017-05-10T12:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171734#M45791</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/18135/umairahmed.html" nodeid="18135"&gt;@umair ahmed&lt;/A&gt; &lt;/P&gt;&lt;P&gt;I am not a Windows Admin and could not tell you off teh top of my head.&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 19:36:11 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171734#M45791</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2017-05-10T19:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171735#M45792</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/525/mclark.html" nodeid="525"&gt;@Matt Clarke&lt;/A&gt;&lt;/P&gt;&lt;P&gt;thanks Matt for your help&lt;/P&gt;&lt;P&gt;umair&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 19:57:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/171735#M45792</guid>
      <dc:creator>umair_ahmed</dc:creator>
      <dc:date>2017-05-10T19:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/297335#M45793</link>
      <description>&lt;P&gt;Hi umair,&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/50133"&gt;@umair_ahmed&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/35453"&gt;@Wynner&lt;/a&gt;&amp;nbsp;,&amp;nbsp;@&lt;A href="https://community.cloudera.com/users/525/mclark.html" rel="user" target="_blank"&gt;Matt Clarke&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The retry mechanism of the unmatched records from the invoke HTTP which was very helpful. Could you please more elaborate information on the advanced settings of the Update attribute. And the Route attribute and Execute stream command.&lt;/P&gt;&lt;P&gt;1) 5 times it needs to retry but only four times it has been mentioned in advanced property of the update attribute. And the expression on the advanced setting of the update attribute needs to be :&amp;nbsp;${retry.counter:replaceNull('0'):equals('1')} whether it needs to be in the incremented fashion like&amp;nbsp;&lt;/P&gt;&lt;P&gt;sleeponeminute -&amp;gt;&amp;nbsp;${retry.counter:replaceNull('0'):equals('1')}&lt;/P&gt;&lt;P&gt;sleepthirtyminute -&amp;gt;&amp;nbsp; ${retry.counter:replaceNull('0'):equals('2')}&lt;/P&gt;&lt;P&gt;sleeponehour -&amp;gt;&amp;nbsp; ${retry.counter:replaceNull('0'):equals('3')}&lt;/P&gt;&lt;P&gt;sleeptwohours -&amp;gt;&amp;nbsp; ${retry.counter:replaceNull('0'):equals('4')}&lt;/P&gt;&lt;P&gt;sleepmaxcount -&amp;gt;&amp;nbsp;${retry.counter:replaceNull('0'):equals('5')} (i.e., the sleeptime for the sleepmaxcount rule set to 180m)&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) For the RouteOnAttribute, I have set the 5 conditions as per your screenshot. I can see the flowfile between the connector updateattribute and RouteOnAttribute then i couldn't see the flowfile in the next connector.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please elaborate more on the property setting of the other two processors Routeon Attribute and Execute StreamCommand(CommandPrompt property: It states take the environmental value ). Working Directory and Output destination attribute could you please explain these properties as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance,&lt;/P&gt;&lt;P&gt;Karthick&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jun 2020 07:21:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/297335#M45793</guid>
      <dc:creator>Karthick93</dc:creator>
      <dc:date>2020-06-04T07:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/297348#M45794</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/78602"&gt;@Karthick93&lt;/a&gt;&amp;nbsp;,&amp;nbsp;As this thread was marked 'Solved' in 2016, you would have a better chance of receiving a useful response by &lt;A href="https://community.cloudera.com/t5/forums/postpage/board-id/Questions" target="_self"&gt;starting a new thread&lt;/A&gt;. This will also provide you with the opportunity to provide details specific to your issue that could aid others in providing a more tailored answer to your question.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jun 2020 09:31:16 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/297348#M45794</guid>
      <dc:creator>VidyaSargur</dc:creator>
      <dc:date>2020-06-04T09:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi: Flowfile retries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/389075#M45795</link>
      <description>&lt;P&gt;The template is not working now. Are there any alternatives??&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 09:49:33 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Flowfile-retries/m-p/389075#M45795</guid>
      <dc:creator>Shakti</dc:creator>
      <dc:date>2024-06-12T09:49:33Z</dc:date>
    </item>
  </channel>
</rss>

