From: Dan Mick <dan.mick@inktank.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Mark Nelson <mark.nelson@inktank.com>,
Matthias Urlichs <matthias@urlichs.de>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph and efficient access of distributed resources
Date: Mon, 15 Apr 2013 15:25:25 -0700 [thread overview]
Message-ID: <516C7E55.1050801@inktank.com> (raw)
In-Reply-To: <CAJH6TXgurT4yUshaH4QOgUKOaB3DqQd1-=HPshp+eH5HB7p3Hg@mail.gmail.com>
On 04/15/2013 01:06 PM, Gandalf Corvotempesta wrote:
> 2013/4/12 Mark Nelson <mark.nelson@inktank.com>
>
>> Currently reads always come from the primary OSD in the placement group
>> rather than a secondary even if the secondary is closer to the client.
>>
>
> In this way, only one OSD will be involved in reading an object, this will
> result in a bottleneck if multiple clients needs to access to the same file.
>
> For example, a 3KB CSS file served by a webserver to 400 users, will be
> read just from one OSD. 400 users directed to 1 OSD while (in case of
> replica 3) other 2 OSDs are available?
Yes. Consistency across the cluster is dependent on this scheme, currently.
next prev parent reply other threads:[~2013-04-15 22:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 3:59 ceph and efficient access of distributed resources Matthias Urlichs
2013-04-12 16:08 ` Mark Nelson
2013-04-12 16:20 ` Gregory Farnum
2013-04-13 2:32 ` Chen, Xiaoxi
2013-04-15 16:42 ` Gregory Farnum
2013-04-15 23:14 ` Chen, Xiaoxi
2013-04-15 20:06 ` Gandalf Corvotempesta
2013-04-15 22:25 ` Dan Mick [this message]
2013-04-15 22:38 ` Mark Kampe
2013-04-16 7:20 ` Gandalf Corvotempesta
2013-04-16 13:59 ` Sage Weil
2013-04-16 14:18 ` Mark Kampe
2013-04-16 20:06 ` Gandalf Corvotempesta
2013-04-16 20:44 ` Mark Kampe
2013-04-17 7:22 ` Gandalf Corvotempesta
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=516C7E55.1050801@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.com \
--cc=mark.nelson@inktank.com \
--cc=matthias@urlichs.de \
/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.