Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to configure news servers as optional #155

Closed
hugbug opened this issue Jan 14, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@hugbug
Copy link
Member

commented Jan 14, 2016

Currently all news servers are expected to work. The program doesn't go to upper level servers until servers on current level were tried. Otherwise a temporary connection error (on unlimited server) could exhaust block servers of upper levels.

However for certain servers (for example free or other unreliable news servers) it would be of benefit if the program could ignore them if they don't work properly.

Also see forum topic Skip server it it's not available.

@hugbug hugbug added the feature label Jan 14, 2016

@hugbug hugbug added this to the v17.0 milestone Jan 14, 2016

@Prinz23

This comment has been minimized.

Copy link

commented Feb 20, 2016

One thing would here be: how would be grouped servers (same level) handled here?

Since it's possible that one has multiple free accounts (that have to renewed/reactivated from time to time) at the same level grouped, normally if they work the grouping helps not to hit the others, but in case of a authentication failure this could be not be desired.

hugbug added a commit that referenced this issue Mar 30, 2016

hugbug added a commit that referenced this issue Mar 30, 2016

@hugbug

This comment has been minimized.

Copy link
Member Author

commented Mar 30, 2016

From (updated) doc:
Marking server as optional tells NZBGet to ignore this server if a connection to this server cannot be established. Normally NZBGet doesn't try upper-level servers before all servers on current level were tried. If a connection to server fails NZBGet waits until the server becomes available (it may try others from current level at this time). This is usually what you want to avoid exhausting of (costly) upper level servers if one of main servers is temporary unavailable. However for less reliable servers you may prefer to ignore connection errors and go on with higher-level servers instead.

@hugbug

This comment has been minimized.

Copy link
Member Author

commented Mar 30, 2016

One thing would here be: how would be grouped servers (same level) handled here?

That's good that you asked. This is how I've implemented it:

In a case of connection errors (or authorization errors) the servers are handled independently. If one fails all others of the same group are tried nonetheless.

If however a server fails because of missing article the others of the same group are not be tried.

hugbug added a commit that referenced this issue Apr 2, 2016

@hugbug hugbug closed this Apr 2, 2016

hugbug added a commit that referenced this issue Oct 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.