Lowering RSSSyncInterval minimum #1464

Closed
opened 2026-02-20 04:14:53 -05:00 by deekerman · 7 comments
Owner

Originally created by @pentaflake on GitHub (May 11, 2017).

Is there any way the hard coded minimum can be adjusted to allow for lower values such as 5 minutes.

Edit: This is actually a bad idea as pointed out below, putting one implemention of the suggested solution here instead.
https://github.com/Zymest/autodl-curl-sonarr

Originally created by @pentaflake on GitHub (May 11, 2017). Is there any way the hard coded minimum can be adjusted to allow for lower values such as 5 minutes. Edit: This is actually a bad idea as pointed out below, putting one implemention of the suggested solution here instead. https://github.com/Zymest/autodl-curl-sonarr
Author
Owner

@Grimeton commented on GitHub (May 11, 2017):

Hi,

# sqlite3 nzbdrone.db
sqlite> update ScheduledTasks set Interval=5 where TypeName='NzbDrone.Core.Indexers.RssSyncCommand';
sqlite > \q
#

Try this. But yes, it will only work if the interval > 10.

Cu

@Grimeton commented on GitHub (May 11, 2017): Hi, ``` # sqlite3 nzbdrone.db sqlite> update ScheduledTasks set Interval=5 where TypeName='NzbDrone.Core.Indexers.RssSyncCommand'; sqlite > \q # ``` Try this. But yes, it will only work if the interval > 10. Cu
Author
Owner

@pentaflake commented on GitHub (May 11, 2017):

That did not take upon starting sonarr again it shows as 10 minutes still on the tasks page under system.

Rss Sync 10 minutes May 11 2017 5:39pm May 11 2017 5:49pm

@pentaflake commented on GitHub (May 11, 2017): That did not take upon starting sonarr again it shows as 10 minutes still on the tasks page under system. Rss Sync 10 minutes May 11 2017 5:39pm May 11 2017 5:49pm
Author
Owner

@markus101 commented on GitHub (May 12, 2017):

TaskManager enforces a minimum of 10 minutes, though that's not the only place it's enforced as there is also validation when saving the setting.

5 minutes is aggressive for RSS and our concern with opening it up is people will needlessly set it to 5 minutes, burn through API calls and have indexers annoyed by it to the point where Sonarr is banned. Banning is pretty extreme, but it's been known to happen to some clients.

Quick grabbing at low intervals is really best left to something (an IRC bot for example) feeding Sonarr releases to see if they are wanted, using Sonarr's API: https://github.com/Sonarr/Sonarr/wiki/Release-Push instead of Sonarr checking an RSS feed frequently.

Which sites suggest a 5 minute interval for their RSS feed?

@markus101 commented on GitHub (May 12, 2017): `TaskManager` enforces a minimum of 10 minutes, though that's not the only place it's enforced as there is also validation when saving the setting. 5 minutes is aggressive for RSS and our concern with opening it up is people will needlessly set it to 5 minutes, burn through API calls and have indexers annoyed by it to the point where Sonarr is banned. Banning is pretty extreme, but it's been known to happen to some clients. Quick grabbing at low intervals is really best left to something (an IRC bot for example) feeding Sonarr releases to see if they are wanted, using Sonarr's API: https://github.com/Sonarr/Sonarr/wiki/Release-Push instead of Sonarr checking an RSS feed frequently. Which sites suggest a 5 minute interval for their RSS feed?
Author
Owner

@pentaflake commented on GitHub (May 12, 2017):

I can see the reasoning behind that then, better to leave it where it is. I will have to look into using the release push api calls to send releases to Sonarr instead. It actually seems like the more logical approach and it looks like there is already someone who has a simple implementation via autodl-irssi. https://github.com/Zymest/autodl-curl-sonarr

I guess this can be closed then. Thank you for the reasoning and suggestion.

@pentaflake commented on GitHub (May 12, 2017): I can see the reasoning behind that then, better to leave it where it is. I will have to look into using the release push api calls to send releases to Sonarr instead. It actually seems like the more logical approach and it looks like there is already someone who has a simple implementation via autodl-irssi. https://github.com/Zymest/autodl-curl-sonarr I guess this can be closed then. Thank you for the reasoning and suggestion.
Author
Owner

@Taloth commented on GitHub (May 13, 2017):

more logical approach

It's faster too, matter of seconds instead of minutes. But it hinges on the tracker having an IRC announce channel.

@markus101 How about leave the issue open to add the explanation to the UI?

@Taloth commented on GitHub (May 13, 2017): > more logical approach It's faster too, matter of seconds instead of minutes. But it hinges on the tracker having an IRC announce channel. @markus101 How about leave the issue open to add the explanation to the UI?
Author
Owner

@markus101 commented on GitHub (May 13, 2017):

Add an explanation why 10 minutes is the minimum or that using the release/push endpoint would be better for faster grabbing?

@markus101 commented on GitHub (May 13, 2017): Add an explanation why 10 minutes is the minimum or that using the release/push endpoint would be better for faster grabbing?
Author
Owner

@Taloth commented on GitHub (May 13, 2017):

Both, I suppose. I'd like people to get to the same realization that using the push api is so much better than settings rss to 5 min, to avoid the 'but I need' discussion.

@Taloth commented on GitHub (May 13, 2017): Both, I suppose. I'd like people to get to the same realization that using the push api is so much better than settings rss to 5 min, to avoid the 'but I need' discussion.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Sonarr#1464
No description provided.