Hi Ryan, No, I cannot see any error inside the indexing error topic. Also, the number of tuples is emitted and transferred to the error indexing bolt is zero!
On Sat, Apr 22, 2017 at 12:29 AM, Ryan Merriman <merrim...@gmail.com> wrote: > Do you see any errors in the error* index in Elasticsearch? There are > several catch blocks across the different topologies that transform errors > into json objects and forward them on to the indexing topology. If you're > not seeing anything in the worker logs it's likely the errors were captured > there instead. > > Ryan > > On Fri, Apr 21, 2017 at 9:19 AM, Ali Nazemian <alinazem...@gmail.com> > wrote: > >> No everything is fine at the log level. Also, when I checked resource >> consumption at the workers, there had been plenty resources still available! >> >> On Fri, Apr 21, 2017 at 10:04 PM, Casey Stella <ceste...@gmail.com> >> wrote: >> >>> Seeing anything in the storm logs for the workers? >>> >>> On Fri, Apr 21, 2017 at 07:41 Ali Nazemian <alinazem...@gmail.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> After I tried to tune the Metron performance I have noticed the rate of >>>> failure for the indexing/enrichment topologies are very high (about 95%). >>>> However, I can see the messages in Elasticsearch. I have tried to increase >>>> the timeout value for the acknowledgement. It didn't fix the problem. I can >>>> set the number of acker executors to 0 to temporarily fix the problem which >>>> is not a good idea at all. Do you have any idea what have caused such >>>> issue? The percentage of failure decreases by reducing the number of >>>> parallelism, but even without any parallelism, it is still high! >>>> >>>> Cheers, >>>> Ali >>>> >>> >> >> >> -- >> A.Nazemian >> > > -- A.Nazemian
