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

Aggregation Spouts to use shard request cache #429

Closed
jnioche opened this Issue Mar 1, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@jnioche
Member

jnioche commented Mar 1, 2017

See https://www.elastic.co/guide/en/elasticsearch/reference/2.4/shard-request-cache.html

This would make the aggregations faster but depends on the value of the refresh interval. We'd need to change the logic around the nextFetchDate query so that we reuse an existing value unless it does not return any results. This alone would also make the search faster as we'd query a diminishing set of documents.

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche Mar 30, 2017

Member

Note: cache is disabled by default in ES 2.x but enabled in 5.x

Member

jnioche commented Mar 30, 2017

Note: cache is disabled by default in ES 2.x but enabled in 5.x

@jnioche jnioche closed this in 67e483f Apr 19, 2017

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche Apr 19, 2017

Member

The logic is now to reset the nextFetchDate only when the number of buckets is 0. We'll refine the mechanism in #452

Member

jnioche commented Apr 19, 2017

The logic is now to reset the nextFetchDate only when the number of buckets is 0. We'll refine the mechanism in #452

@jnioche jnioche added this to the 1.5 milestone Apr 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment