From: David McBride <dwm37@cam.ac.uk>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
Sebastien Han <sebastien.han@enovance.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Weil Sage <sage@inktank.com>,
Patrick McGarry <patrick@inktank.com>
Subject: Re: Ceph Ansible Repo
Date: Thu, 06 Mar 2014 12:07:46 +0000 [thread overview]
Message-ID: <53186512.6080405@cam.ac.uk> (raw)
In-Reply-To: <CAJH6TXiWC0yRWSgU8B0=-mNDXc0tdQ62O3=K2t+Dq5T3emSCOg@mail.gmail.com>
On 06/03/14 09:36, Gandalf Corvotempesta wrote:
> Hi to all.
> Some question about ansible repo.
>
> 1. is possible to specify multiple journal devices for each OSD node?
> We have OSD with 12 spinning disks and 2 SSD as journal. We would like
> to use SSD1 for OSD1 to 6 and SSD2 for OSD 7 to 12. Is this possible ?
One option I'm currently testing is whereby the two SSDs in a node are
stitched together into a Linux software-RAID striped array, and then
allocate the journal partitions on the resulting /dev/md device.
This is currently working well, save that the default udev rules for
mapping OSDs explicitly skip over md journal devices; removing the
"|md*" term in the relevant ruleset resolves this problem. (This is in
my workqueue to report as a bug.)
This causes the IO load to be nicely balanced across the two SSDs,
removing any hot spots, at the cost of enlarging the failure domain of
the loss of an SSD from half a node to a full node.
One potential optimization which I haven't yet investigated is to see
whether moving the XFS filesystem journal, in addition to the OSd
journal, might result in an improvement in performance — in particular
on nodes which are equipped with slower 'green' drives.
This is not something that ceph-deploy currently makes easy; if, as I
expect, I find myself re-implementing the ceph-deploy functions in terms
of Ansible rules — perhaps using LVM rather than GPT partitions? — I may
then be able to try some experiments.
Kind regards,
David
--
David McBride <dwm37@cam.ac.uk>
Unix Specialist, University Computing Service
--
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:[~2014-03-06 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 23:26 Ceph Ansible Repo Sebastien Han
2014-03-03 2:59 ` Ian Colle
2014-03-03 8:49 ` Sebastien Han
2014-03-03 15:30 ` Travis Rhoden
2014-03-03 17:13 ` Ian Colle
2014-03-03 18:13 ` Sebastien Han
2014-03-06 9:36 ` Gandalf Corvotempesta
2014-03-06 10:14 ` Sebastien Han
2014-03-06 10:28 ` Gandalf Corvotempesta
2014-03-06 10:42 ` Sebastien Han
2014-03-06 10:43 ` Gandalf Corvotempesta
2014-03-06 12:07 ` David McBride [this message]
2014-03-06 13:19 ` Gandalf Corvotempesta
2014-03-06 13:28 ` David McBride
2014-03-06 16:31 ` Sebastien Han
2014-03-06 16:45 ` Gandalf Corvotempesta
2014-03-06 18:05 ` Sebastien Han
2014-03-07 13:09 ` Sebastien Han
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=53186512.6080405@cam.ac.uk \
--to=dwm37@cam.ac.uk \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.com \
--cc=patrick@inktank.com \
--cc=sage@inktank.com \
--cc=sebastien.han@enovance.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.