From: Martin Fick <mogulguy@yahoo.com>
To: ceph-devel@vger.kernel.org
Subject: RBD/OSD questions
Date: Thu, 6 May 2010 09:07:13 -0700 (PDT) [thread overview]
Message-ID: <853578.71750.qm@web36102.mail.mud.yahoo.com> (raw)
I have a few more questions.
-Can files stored in the OSD heal "incrementally"?
Suppose there are 3 replicas for a large file and that
a small byte range change occurs while replica 3 is
down. Will replica 3 heal efficiently when it
returns? Will only the small changed byte range
be transferred?
-Also, can reads be spreadout over replicas?
This might be a nice optimization to reduce seek
times under certain conditions, when there are no
writers or the writer is the only reader (and thus
is aware of all the writes even before they
complete). Under these conditions it seems like it
would be possible to not enforce the "tail reading"
order of replicas and thus additionally benefit
from "read stripping" across the replicas the way
many raid implementations do with RAID1.
I thought that this might be particularly useful
for RBD when it is used exclusively (say by mounting
a local FS) since even with replicas, it seems like
it could then relax the replica tail reading
constraint.
Any thoughts? Thanks,
-Martin
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-05-06 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 16:07 Martin Fick [this message]
2010-05-06 17:14 ` RBD/OSD questions Sage Weil
-- strict thread matches above, loose matches on Subject: below --
2010-05-06 21:02 Martin Fick
2010-05-06 21:22 ` Sage Weil
2010-05-06 21:24 ` Cláudio Martins
2010-05-06 21:31 ` Sage Weil
2010-05-06 21:41 ` Martin Fick
2010-05-06 21:54 ` Gregory Farnum
2010-05-06 22:20 ` Sage Weil
2010-05-07 16:38 ` Andreas Grimm
2010-05-07 16:43 ` Sage Weil
2010-05-11 8:39 ` Anton
2010-05-11 16:26 ` Sage Weil
2010-05-06 22:28 Martin Fick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=853578.71750.qm@web36102.mail.mud.yahoo.com \
--to=mogulguy@yahoo.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.