From: Wido den Hollander <wido@widodh.nl>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Andrew Thrift <andyonfire@gmail.com>,
ceph-devel@vger.kernel.org, mark.nelson@inktank.com
Subject: Re: Large numbers of OSD per node
Date: Tue, 06 Nov 2012 10:46:32 +0100 [thread overview]
Message-ID: <5098DC78.1040303@widodh.nl> (raw)
In-Reply-To: <CAJH6TXhscSv9-JpzP=+ZE421ojGh4NtgycNt929QVNXNwCmzMQ@mail.gmail.com>
On 06-11-12 10:36, Gandalf Corvotempesta wrote:
> 2012/11/6 Wido den Hollander <wido@widodh.nl>:
>> You shouldn't only think about a complete failure solution. The distributed
>> architecture of Ceph also gives you the freedom to take out a node whenever
>> you want to do maintenance or just don't trust the node and you want to
>> investigate.
>>
>> The scenario is still the same. Use smaller nodes so taking out one node
>> (for what reason) doesn't impact your cluster that much.
>
> Here:
> http://ceph.com/docs/master/install/hardware-recommendations/
> is wrote that a production cluster has been made with many R515 with
> 12 disks of 3TB each. This give us 36TB of storage.
>
> is this configuration considered good ? I'm planning to have the same server.
> --
It works for them. There is no journaling though, but this setup is only
being used for the RADOS Gateway, not for RBD.
You might want to insert a couple of SSDs in there to do journaling for you.
But the rule also applies here. When you use 3 of these machines, when
loosing one, you will lose 33% of your cluster.
The setup described on that page has 90 nodes, so one node failing is a
little over 1% of the cluster which fails.
Wido
> 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-11-06 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 7:14 Large numbers of OSD per node Andrew Thrift
2012-11-05 11:01 ` Wido den Hollander
2012-11-05 12:45 ` Mark Nelson
2012-11-06 2:05 ` Andrew Thrift
2012-11-06 9:10 ` Wido den Hollander
2012-11-06 9:36 ` Gandalf Corvotempesta
2012-11-06 9:46 ` Wido den Hollander [this message]
2012-11-06 10:20 ` Gandalf Corvotempesta
2012-11-06 10:24 ` Gandalf Corvotempesta
2012-11-06 11:05 ` Stefan Kleijkers
2012-11-06 11:31 ` Gandalf Corvotempesta
2012-11-06 11:51 ` Stefan Kleijkers
2012-11-06 12:51 ` 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=5098DC78.1040303@widodh.nl \
--to=wido@widodh.nl \
--cc=andyonfire@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.com \
--cc=mark.nelson@inktank.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.