Is is possible to change the indexer timeout that Sonarr uses when doing RSS searches? I use NZB Hydra which aggregates all the nzb’s from my indexers and removes the duplicates. Sometimes this can take over 100 seconds to process all the results when I enable a lot of indexers. It may timeout a few times a day in Sonarr and potentially allow an nzb to be missed. Possible?
First question is: Why is it that slow? It’s not like a few seconds, but a more than a minute? that feels extreme.
First, it calls the all the indexers using their api and gets the nzb results. That takes about 8-10 seconds. The rest of the time is taken up by processing the search results. It logs the nzbs and filters out the duplicates displaying only unique nzbs. Each indexer takes about 4-8 seconds with my htpc’s slow processor. If I enable all of my indexers, which is 15, then it usually takes over the 100 seconds.
Most api calls can be done in parallel, and NzbHydra does that, afaik, so 8-10 seconds to get all results is odd.
The processing itself seems slow, it should be able to sift through the results quicker, but that’s likely due to the slow hardware, but might be possible to optimize in NzbHydra.
Either way, 100 sec is extreme, and would make a lot of stuff in Sonarr painfully slow as well. it’s potentially a cascade of timeouts to the UI as well.
It isn’t possible to adjust the timeout (of the top of my head, I don’t know what it’s set to atm), considering the fairly unique circumstances I don’t see a reason to increase the timeout nor add an option for it.
I actually think this is a good idea. I’ve been wondering this too. I have about 8 indexers set up in NZBHydra with a timeout of 30 seconds. Lately, it seems that Sonarr doesn’t give NZBhydra enough time to finish.
Just a thought.
NZBhydra updated their code a few weeks ago that sped it up quite a bit. Are you updated to the latest version? I no longer have this problem I mentioned in the first post.
Yeah, I have. What is the timeout you have set?
My indexer timeout is set to 10. However, a solution may be found in a different setting. In the main config you find an option “Store results for…”. Lower that to 2 days or less. Restart hydra. Try again. I guess when the database fills up, it slows down the nzb analysis dramatically.
That setting reduces how long nzbhydra keeps the link to the nzb valid. For example, if sonarr searches on Monday and you click download button in CP more than 48 hours later on Wednesday, then it won’t work.
Humm, interesting! I’ll check it out! THANKS!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.