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.

Sign up for GitHub

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

Jump to bottom

ES change value of es.status.reset.fetchdate.after #590

Closed
jnioche opened this issue Jul 6, 2018 · 0 comments
Closed

ES change value of es.status.reset.fetchdate.after #590

jnioche opened this issue Jul 6, 2018 · 0 comments
Labels
elasticsearch
Milestone
1.11

Comments

@jnioche
Copy link
Contributor

jnioche commented Jul 6, 2018

By default it is set to -1, which means that the same nextFetchDate will be reused as long as it returns results. If a single site has loads of URLs scheduled at the same time, e.g. coming from a sitemap, only URLs from that site will be fetched.

Will change to 120 secs by default, can always be changed by the users.
@jnioche jnioche added this to the 1.11 milestone Jul 6, 2018
@jnioche jnioche closed this as completed in cdf24a4 Jul 6, 2018
ndtreviv pushed a commit to CameraForensics/storm-crawler that referenced this issue Apr 17, 2023
@sebastian-nagel @jnioche
Upgrade WARC module to latest version of storm-hdfs, fixes apache#590 (…
0afe3ed 
…apache#520)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
elasticsearch
Projects
None yet
Milestone
1.11
Development

No branches or pull requests
1 participant
@jnioche