High number of failed messages from MqttSpout
Hi storm experts, As you can see from this diagram, mqtt_spout appears to have high number of failed messages. I have tried following things 1) Set topology.ackers: 0 2) Walk through the topology to see if there are any bolt that does not ack or fail unexpectedly but I didn't see any. 3) Set the message timeout to 1 hours All of above does not work so we are wonderring what are the other options and why it appears to have high fail rate and how to fix it? Regards, Kai
Re: High number of failed messages from MqttSpout
Hi Kai, Seems like tuple timeout errors(no failed tuples in bolts but spout reports failure), Whats the value for max pending spout? Set it to a smaller number like 10 just to test it. and then see how high you can go based on what you doing in your topology. Thanks Ravi. On Thu, Mar 7, 2019 at 2:58 AM 1733208392 <1733208...@qq.com> wrote: > Hi storm experts, > > As you can see from this diagram, mqtt_spout appears to have high number > of failed messages. I have tried following things > 1) Set topology.ackers: 0 > 2) Walk through the topology to see if there are any bolt that does not > ack or fail unexpectedly but I didn't see any. > 3) Set the message timeout to 1 hours > > All of above does not work so we are wonderring what are the other options > and why it appears to have high fail rate and how to fix it? > > Regards, > Kai >
Re: High number of failed messages from MqttSpout
Also some tuples may fail during topology startup due to timeout, if the workers happen to not start at roughly the same time. Den tor. 7. mar. 2019 kl. 07.24 skrev Ravi Sharma : > Hi Kai, > Seems like tuple timeout errors(no failed tuples in bolts but spout > reports failure), Whats the value for max pending spout? > Set it to a smaller number like 10 just to test it. and then see how high > you can go based on what you doing in your topology. > > Thanks > Ravi. > > On Thu, Mar 7, 2019 at 2:58 AM 1733208392 <1733208...@qq.com> wrote: > >> Hi storm experts, >> >> As you can see from this diagram, mqtt_spout appears to have high number >> of failed messages. I have tried following things >> 1) Set topology.ackers: 0 >> 2) Walk through the topology to see if there are any bolt that does not >> ack or fail unexpectedly but I didn't see any. >> 3) Set the message timeout to 1 hours >> >> All of above does not work so we are wonderring what are the other >> options and why it appears to have high fail rate and how to fix it? >> >> Regards, >> Kai >> >
