mirror of
https://github.com/Sonarr/Sonarr.git
synced 2026-03-02 22:57:43 -05:00
Lowering RSSSyncInterval minimum #1464
Labels
No labels
1%
blocked-by: skyhook
bug
connection
discussion
docs
download-client
enhancement
external-bug
indexer
missing-description
mono-bug
naming
needs-to-be-tested
needs-triage
one-day-maybe
parsing
platform: linux
platform: macos
platform: windows
priority:high
priority:low
priority:medium
priority:medium
proposal
skyhook/services
suboptimal
support
task
ui-only
up-for-grabs
v3
v4
waiting-for-contributor
waiting-for-info
wip
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Sonarr#1464
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@Grimeton commented on GitHub (May 11, 2017):
Hi,
Try this. But yes, it will only work if the interval > 10.
Cu
@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
@markus101 commented on GitHub (May 12, 2017):
TaskManagerenforces 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?
@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.
@Taloth commented on GitHub (May 13, 2017):
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?
@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?
@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.