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

doc: document "readforward" and "readproxy" cache mode #7023

Merged
1 commit merged into from Dec 23, 2015

Conversation

tchaikov
Copy link
Contributor

Signed-off-by: Kefu Chai kchai@redhat.com

Signed-off-by: Kefu Chai <kchai@redhat.com>
backing tier for the data. If the read performance of the backing tier is on
a par with that of its cache tier, while its write performance or endurance
falls far behind, this mode might be a better choice.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clients might have a stale read here? e.g. the newly writes are not flushed to the base tier from cache tier, but the read requests are serviced from base tier.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right. that's why i put a precondition here

read objects not yet copied to the cache tier

@zhouyuan
Copy link
Contributor

@tchaikov thanks for the update on doc! This helped a lot.

@ghost ghost self-assigned this Dec 23, 2015
ghost pushed a commit that referenced this pull request Dec 23, 2015
doc: document "readforward" and "readproxy" cache mode

Reviewed-by: Loic Dachary <ldachary@redhat.com>
@ghost ghost merged commit 03f9307 into ceph:master Dec 23, 2015
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants