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

Investigate resolver updates #118

Open
spacemansteve opened this issue Feb 24, 2020 · 2 comments
Open

Investigate resolver updates #118

spacemansteve opened this issue Feb 24, 2020 · 2 comments

Comments

@spacemansteve
Copy link
Contributor

spacemansteve commented Feb 24, 2020

We have seen some incidents where resolver has outdated link data while solr has current/updated data. How is that happening? Is there a bug skips updates to the resolver under certain conditions? If there is an error while updating the resolver will it be retried? Did the testing of the solr index rebuild contribute to this problem? Was it just caused by only updating solr when responding to special requests to process bibcodes (e.g., using -r s rather than -r).

@spacemansteve
Copy link
Contributor Author

Sergi noted a bug in tasks.py. The code fails to use the correct column name for the datalinks_checksum. So, it fails to appreciate when the resolver data has not changed and always sends an update to resolver.

@spacemansteve
Copy link
Contributor Author

Sergi noted a bug in app.py. The processed column will be updated even when, for example, the resolver updated failed. This will prevent a failed bibcode from being reset on subsequent runs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant