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

Add optional S3 streaming for cache nodes #1079

Merged
merged 2 commits into from
Oct 1, 2024
Merged

Conversation

bryanlb
Copy link
Contributor

@bryanlb bryanlb commented Sep 18, 2024

Summary

Adds an experimental flag for the cache nodes, that optionally streams in the data from object storage. This removes the requirement for disk for cache nodes, enabling switching to significantly cheaper storage types.

Current implementation still results in the assignments still being "downloaded" and "initialized," but transparent to Lucene this is fetching with block-level caches into memory at the time of request.

To use set:

-Dastra.s3Streaming.enabled=true

optionally:

-Dastra.s3Streaming.pageSize=2097152

@bryanlb bryanlb mentioned this pull request Sep 18, 2024
2 tasks
Base automatically changed from bburkholder/assorted-enhancements to master September 18, 2024 23:56
@bryanlb bryanlb force-pushed the bburkholder/s3-streaming branch 3 times, most recently from 7119e67 to 9d227af Compare October 1, 2024 18:14
@bryanlb bryanlb marked this pull request as ready for review October 1, 2024 18:15
@bryanlb bryanlb merged commit aaab576 into master Oct 1, 2024
2 checks passed
@bryanlb bryanlb deleted the bburkholder/s3-streaming branch October 1, 2024 23:45
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

Successfully merging this pull request may close these issues.

2 participants