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
Having run a couple of heavy sets of seeds through the Redis Frontier, and after PAUSING the crawl, some queues are in qs:active and not in qs:scheduled - specifically:
and the timestamps are significantly older than those in qs:scheduled indicating that they've been forgotten. They are in qs:known so scanning that would bring it back.
Track down if this is a problem!
Determine how to properly evaluate the reliabilty of a whole replacement frontier!
The text was updated successfully, but these errors were encountered:
Having run a couple of heavy sets of seeds through the Redis Frontier, and after PAUSING the crawl, some queues are in
qs:active
and not inqs:scheduled
- specifically:and the timestamps are significantly older than those in
qs:scheduled
indicating that they've been forgotten. They are inqs:known
so scanning that would bring it back.The text was updated successfully, but these errors were encountered: