From: Stefan Kleijkers <stefan@unilogicnetworks.net>
To: Madhusudhana U <madhusudhana.u.acharya@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Can we have mutiple OSD in a single machine
Date: Wed, 11 Apr 2012 09:53:38 +0200 [thread overview]
Message-ID: <4F853882.8010001@unilogicnetworks.net> (raw)
In-Reply-To: <loom.20120411T093935-734@post.gmane.org>
Hello,
Yes that's no problem. I'm using that configuration for some time now.
Just generate a config with multiple OSD clauses with the same node/host.
With the newer ceph version mkcephfs is smart enough to detect the osd's
on the same node and will generate a crushmap whereby the objects get
replicated to different nodes.
I didn't see any impact on the performance (if you have enough
processing power, because you need more of that).
I wanted to use just a few OSD's per node with mdraid, so I could use
RAID6. This way I could swap a faulty disk without bringing the node
down. But I couldn't get it stable with mdraid.
Stefan
On 04/11/2012 09:42 AM, Madhusudhana U wrote:
> Hi all,
> I have a system with 2T SATA drive and I want to add it to my ceph
> cluster. I was thinking instead of creating one large OSD, can't
> I have 44 osd's of 450G each ? Is this possible ? if possible, will
> this improve read/write performance ?
>
> Thanks
> __Madhusudhana
>
> --
> 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 prev parent reply other threads:[~2012-04-11 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 7:42 Can we have mutiple OSD in a single machine Madhusudhana U
2012-04-11 7:53 ` Stefan Kleijkers [this message]
2012-04-11 12:42 ` Madhusudhana U
2012-04-11 13:55 ` Tomasz Paszkowski
2012-04-11 14:33 ` Stefan Kleijkers
2012-04-11 9:45 ` Tomasz Paszkowski
2012-04-11 12:38 ` Madhusudhana U
2012-04-11 13:53 ` Tomasz Paszkowski
2012-04-11 16:07 ` Sage Weil
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=4F853882.8010001@unilogicnetworks.net \
--to=stefan@unilogicnetworks.net \
--cc=ceph-devel@vger.kernel.org \
--cc=madhusudhana.u.acharya@gmail.com \
/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.