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

Rora reads could keep replication in mind to avoid unnecessary fallback to proxy #598

Open
domsj opened this issue Jan 27, 2017 · 3 comments

Comments

@domsj
Copy link
Contributor

domsj commented Jan 27, 2017

E.g. in case of replication on an all flash backend multiple fragments of the same chunk are equivalent.
The ocaml code knows about this, and can leverage that. The c++ code however will do a fallback to the proxy in case it can't read from the first fragment of a certain chunk (either because it isn't there, or because the asd is down).

The same applies for an accelerated backend with replication on the cache backend.

@wimpers wimpers added this to the Gilbert milestone Feb 9, 2017
@wimpers
Copy link

wimpers commented May 30, 2017

What about HPRM?

@wimpers wimpers modified the milestones: Roadmap, G May 30, 2017
@domsj
Copy link
Contributor Author

domsj commented May 30, 2017

The pracc server uses the rora code inside, so same issue applies there.
Do note that given the repair-on-partial-read behaviour this isn't too bad...
(Also: how often will the fastest tier/cache use replication?)

@wimpers
Copy link

wimpers commented May 30, 2017

(Also: how often will the fastest tier/cache use replication?)

Hence set to Roadmap ;-)

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