You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, unlike pages and crawl files, errors are only being added to the database at the conclusion of a crawl. The associated API endpoint is pulling them straight from Redis during crawling and then from the db after the crawl. This is perhaps more complex a solution than it needs to be, and also leaves the potential for the crawler pod to be shut down before all errors are read into the database.
We should modify the handling of errors to be similar to crawl pages/files and add them incrementally to the database during crawling by popping them from the Redis queue as they show up.
The text was updated successfully, but these errors were encountered:
Fixes#1558
- Adds crawl errors to database incrementally during crawl rather than
after crawl completes
- Simplifies crawl /errors API endpoint to always return errors from
database
Currently, unlike pages and crawl files, errors are only being added to the database at the conclusion of a crawl. The associated API endpoint is pulling them straight from Redis during crawling and then from the db after the crawl. This is perhaps more complex a solution than it needs to be, and also leaves the potential for the crawler pod to be shut down before all errors are read into the database.
We should modify the handling of errors to be similar to crawl pages/files and add them incrementally to the database during crawling by popping them from the Redis queue as they show up.
The text was updated successfully, but these errors were encountered: