All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
	ceph-devel@vger.kernel.org
Subject: Re: flashcache
Date: Wed, 16 Jan 2013 15:53:20 -0600	[thread overview]
Message-ID: <50F72150.7080002@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301161325280.27925@cobra.newdream.net>

On 01/16/2013 03:29 PM, Sage Weil wrote:
> On Wed, 16 Jan 2013, Gandalf Corvotempesta wrote:
>> In a ceph cluster, flashcache with writeback is considered safe?
>> In case of SSD failure, the flashcache contents should be already been
>> replicated (by ceph) in other servers, right?
>
> This sort of configuration effectively bundles the disk and SSD into a
> single unit, where the failure of either results in the loss of both.
>  From Ceph's perspective, it doesn't matter if the thing it is sitting on
> is a single disk, an SSD+disk flashcache thing, or a big RAID array.  All
> that changes is the probability of failure.
>
> The thing to watch out for *knowing* that the whole is lost when one part
> fails (vs plowing ahead with a corrupt fs).
>
>> I'm planning to use this configuration: Supermicro with 12 spinning
>> disks e 2 SSD.
>> 6 spinning disks will have ceph journal on SSD1, the other 6 disks
>> will have ceph journal on disks2.
>>
>> One OSD for each spinning disk (a single XFS filesystem for the whole disk).
>> XFS metadata to a parition of SSD1
>> XFS flashcache to another partition of SSD1
>>
>> So, 3 partitions for each OSD on the SSD.
>> How big should be these partitions? Any advice?
>>
>> No raid at all, except for 1 RAID-1 volume made with a 10GB partitions
>> on each SSD, for the OS. Log files will be replicated to a remote
>> server, so writes on OS partitions are very very low.
>>
>> Any hint? Adivice? Critics?

Looks like a fun configuration to test!  Having said that, I have no 
idea how stable flashcache is.  It's certainly not something we've used 
in production before!  Keep that in mind.

With only 2 SSDs for 12 spinning disks, you'll need to make sure the 
SSDs are really fast.  I use Intel 520s for testing which are great, but 
I wouldn't use them in  production.  The S3700 might be a good bet at 
larger sizes, but it looks like the 100GB version is a lot slower than 
the 200GB version, and that's still a bit slower than the 400GB version. 
  Assuming you have 10GbE, you'll probably be capped by the SSDs for 
large block sequential workloads.  Having said that, I still think this 
has potential to be a nice setup.  Just be aware that we usually don't 
stick that much stuff on the SSDs!

>
> I would worry that there is a lot of stuff piling onto the SSD and it may
> become your bottleneck.  My guess is that another 1-2 SSDs will be a
> better 'balance', but only experiementation will really tell us that.
>

It'd be amazing if supermicro could cram another 2 SSD slots in the 
back.  Maybe by that time we'll all be using PCIE flash storage though. :)

> Otherwise, those seem to all be good things to put on teh SSD!
>
> sage
> --
> 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
>


  parent reply	other threads:[~2013-01-16 21:53 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 21:22 flashcache Gandalf Corvotempesta
2013-01-16 21:29 ` flashcache Sage Weil
2013-01-16 21:42   ` flashcache Gandalf Corvotempesta
2013-01-16 21:46     ` flashcache Sage Weil
2013-01-16 21:55       ` flashcache Mark Nelson
2013-01-16 21:59         ` flashcache Gandalf Corvotempesta
2013-01-16 21:57       ` flashcache Gandalf Corvotempesta
2013-01-16 21:53   ` Mark Nelson [this message]
2013-01-16 22:04     ` flashcache Gandalf Corvotempesta
2013-01-17  5:47     ` flashcache Stefan Priebe - Profihost AG
2013-01-17 13:34       ` flashcache Mark Nelson
2013-01-17  9:46     ` flashcache Gandalf Corvotempesta
2013-01-17 13:32       ` flashcache Joseph Glanville
2013-01-17 13:37         ` flashcache Mark Nelson
2013-01-17 13:44           ` flashcache Gandalf Corvotempesta
2013-01-17 14:30           ` flashcache Atchley, Scott
2013-01-17 14:48             ` flashcache Gandalf Corvotempesta
2013-01-17 15:00               ` flashcache Atchley, Scott
2013-01-17 15:07                 ` flashcache Andrey Korolyov
2013-01-17 15:47                   ` flashcache Atchley, Scott
2013-01-17 16:39                     ` flashcache Andrey Korolyov
2013-01-20  2:56                       ` flashcache Joseph Glanville
2013-01-21 23:57                         ` flashcache John Nielsen
2013-01-30 20:10                           ` flashcache Joseph Glanville
2013-01-17 15:14                 ` flashcache Gandalf Corvotempesta
2013-01-17 15:50                   ` flashcache Atchley, Scott
2013-01-17 16:01                     ` flashcache Gandalf Corvotempesta
2013-01-17 16:12                       ` flashcache Atchley, Scott
2013-01-17 16:19                         ` flashcache Gandalf Corvotempesta
2013-01-22 21:06                           ` flashcache Atchley, Scott
2013-01-22 21:08                             ` flashcache Atchley, Scott
2013-01-17 16:20                         ` flashcache Stefan Priebe
2013-01-17 16:21                           ` flashcache Gandalf Corvotempesta
2013-01-17 16:24                             ` flashcache Stefan Priebe

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=50F72150.7080002@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=sage@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.