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

partial read behavior on initial failure could be optimized #781

Open
domsj opened this issue Aug 9, 2017 · 0 comments
Open

partial read behavior on initial failure could be optimized #781

domsj opened this issue Aug 9, 2017 · 0 comments

Comments

@domsj
Copy link
Contributor

domsj commented Aug 9, 2017

When the data fragment from which the proxy tries to read a bit of data is unavailable (most likely because the asd is down) there will currently be a fallback to fetch the entire chunk so it can rebuild the missing data fragment (followed by a repair-on-read of the missing fragment).

While functionally correct the proxy could (in case of no compression) instead fetch the right k slices from other available fragments, and erasure decode those to get at the desired piece of data.

This is a lot more lightweight (e.g. fetching k*4KB vs k*4MB), but has a downside that the unavailable data fragment will not be immediately repaired. It should result in a smoother transition (less hiccups) in case an asd (temporarily) goes haywire.

@wimpers wimpers added this to the J milestone Aug 23, 2017
@wimpers wimpers removed this from the J milestone Mar 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants