<?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: Are Failed Messages a Storm Spout Reports Lost? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94619#M7918</link>
    <description>&lt;P&gt;It depends on how the spout is implemented. Lets look at KafkaSpout the failed messages can be for 2 reasons&lt;/P&gt;&lt;P&gt;1. Downstream bolts are failed to process or called collector.fail&lt;/P&gt;&lt;P&gt;2. Downstream bolts are failed to acknowledge the tuple within topology.message.timeout.secs this is 30secs by default. &lt;/P&gt;&lt;P&gt;In two cases you can see the spout failed number go up. But kafkaSpout will replay until the messages are acknowledged . If you are using Acking with storm-core topology it guarantees at least once delivery, i.e there might be duplicates but no message loss.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2015 22:49:34 GMT</pubDate>
    <dc:creator>schintalapani</dc:creator>
    <dc:date>2015-09-30T22:49:34Z</dc:date>
    <item>
      <title>Are Failed Messages a Storm Spout Reports Lost?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94618#M7917</link>
      <description>&lt;P&gt;If a Storm Spourt reports X number of messages as failed, are these messages lost and were not replayed? So these messages were never processed by the toplogoy? How to find out which messages were effected?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2015 21:53:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94618#M7917</guid>
      <dc:creator>hkropp</dc:creator>
      <dc:date>2015-09-30T21:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Are Failed Messages a Storm Spout Reports Lost?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94619#M7918</link>
      <description>&lt;P&gt;It depends on how the spout is implemented. Lets look at KafkaSpout the failed messages can be for 2 reasons&lt;/P&gt;&lt;P&gt;1. Downstream bolts are failed to process or called collector.fail&lt;/P&gt;&lt;P&gt;2. Downstream bolts are failed to acknowledge the tuple within topology.message.timeout.secs this is 30secs by default. &lt;/P&gt;&lt;P&gt;In two cases you can see the spout failed number go up. But kafkaSpout will replay until the messages are acknowledged . If you are using Acking with storm-core topology it guarantees at least once delivery, i.e there might be duplicates but no message loss.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2015 22:49:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94619#M7918</guid>
      <dc:creator>schintalapani</dc:creator>
      <dc:date>2015-09-30T22:49:34Z</dc:date>
    </item>
    <item>
      <title>Re: Are Failed Messages a Storm Spout Reports Lost?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94620#M7919</link>
      <description>&lt;P&gt;Storm platform assumes that all messages will be processed successfully. This implies that any messages marked as "failed" were also replayed and successfully processed. I don't believe that failed and replayed messages are identified in a unique way by the platform.&lt;/P&gt;&lt;P&gt;&lt;A href="https://storm.apache.org/documentation/Guaranteeing-message-processing.html"&gt;Documentation reference&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"This means the (failed) message is not actually taken off the queue yet, but instead placed in a "pending" state waiting for acknowledgement that the message is completed. While in the pending state, a message will not be sent to other consumers of the queue."&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2015 22:58:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94620#M7919</guid>
      <dc:creator>wfloyd</dc:creator>
      <dc:date>2015-09-30T22:58:15Z</dc:date>
    </item>
    <item>
      <title>Re: Are Failed Messages a Storm Spout Reports Lost?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94621#M7920</link>
      <description>&lt;P&gt;In storm version apache-storm-1.0.2 , there a field called maxRetries in the retryservice provided for the kafkaSpout and when a bolt fails for &amp;gt; maxretries the message is acked by spout.So does this mean the message them is removed from the kafka queue. If so, with out processing a message we ae actually removing it? Isn't that bad? &lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2016 17:20:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Are-Failed-Messages-a-Storm-Spout-Reports-Lost/m-p/94621#M7920</guid>
      <dc:creator>sushmithavangal</dc:creator>
      <dc:date>2016-11-17T17:20:58Z</dc:date>
    </item>
  </channel>
</rss>

