Track searchapi_host and data node prioritization #173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Often the user will specify the index node as searchapi_host in a selection file.
As Synda runs, a failure downloading a file may lead to a new search and a retry at whatever url the search discovered.
The new search should use the index node specified in the selection file. These changes keep track of searchapi_host by including it in the appropriate file and transfer objects.
That change overlaps with an improvement in the prioritization of data nodes in sdnexturl.py. So this improvement is also included in this branch and pull request.