From: Jimmy Tang <jtang@tchpc.tcd.ie>
To: ceph-devel@vger.kernel.org
Subject: issues with adjusting the crushmap in 0.51
Date: Thu, 6 Sep 2012 18:58:21 +0100 [thread overview]
Message-ID: <20120906175821.GA32205@tchpc.tcd.ie> (raw)
[-- Attachment #1: Type: text/plain, Size: 3696 bytes --]
Hi All,
I've been playing around with 0.51 of ceph on two test machines in
work, I was experimenting with adjusting the crushmap to change from
replicating across osd's to replicating across hosts. When I change
the rule for my data pool from type osd to type host, compile up the
crushmap and then a "ceph osd setcrushmap -i crush.new" it crashes my
monitor if I have one running, if I have two, then one of them crashes
and the process just hangs and leaves my test filesystem in an unclean
state.
I changed the rule data {} to this
rule data {
ruleset 0
type replicated
min_size 1
max_size 10
step take default
step choose firstn 0 type host
step emit
}
Are there any constraints for changing the rules on where things get
replicated? i.e. to go from osd to host to rack with the data and
metadata?
Here's my ceph.conf file and crushmap before the changes
[global]
#auth supported = cephx
#keyring = /etc/ceph/ceph.keyring
filestore xattr use omap = true
[osd]
osd journal size = 1000
filestore xattr use omap = true
[mon.a]
host = 134.226.112.194
mon addr = 134.226.112.194:6789
mon data = /data/mon.$id
[mon.b]
host = 134.226.112.138
mon addr = 134.226.112.138:6789
mon data = /home/mon.$id
[mds.a]
host = 134.226.112.194
mon data = /data/mds.$id
[mds.b]
host = 134.226.112.138
mon data = /home/mds.$id
[osd.0]
host = 134.226.112.194
osd data = /data/osd.$id
osd journal = /data/osd.$id.journal
[osd.1]
host = 134.226.112.194
osd data = /data$id/osd.$id
osd journal = /data$id/osd.$id.journal
[osd.2]
host = 134.226.112.138
osd data = /home/osd.$id
osd journal = /home/osd.$id.journal
My crushmap
# begin crush map
# devices
device 0 osd.0
device 1 osd.1
device 2 osd.2
# types
type 0 osd
type 1 host
type 2 rack
type 3 row
type 4 room
type 5 datacenter
type 6 pool
# buckets
host 134.226.112.194 {
id -2 # do not change unnecessarily
# weight 2.000
alg straw
hash 0 # rjenkins1
item osd.1 weight 1.000
item osd.0 weight 1.000
}
host 134.226.112.138 {
id -4 # do not change unnecessarily
# weight 1.000
alg straw
hash 0 # rjenkins1
item osd.2 weight 1.000
}
rack rack-1 {
id -3 # do not change unnecessarily
# weight 3.000
alg straw
hash 0 # rjenkins1
item 134.226.112.194 weight 2.000
item 134.226.112.138 weight 1.000
}
pool default {
id -1 # do not change unnecessarily
# weight 2.000
alg straw
hash 0 # rjenkins1
item rack-1 weight 2.000
}
# rules
rule data {
ruleset 0
type replicated
min_size 1
max_size 10
step take default
step choose firstn 0 type osd
step emit
}
rule metadata {
ruleset 1
type replicated
min_size 1
max_size 10
step take default
step choose firstn 0 type osd
step emit
}
rule rbd {
ruleset 2
type replicated
min_size 1
max_size 10
step take default
step choose firstn 0 type osd
step emit
}
Jimmy
--
Jimmy Tang
Trinity Centre for High Performance Computing,
Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
http://www.tchpc.tcd.ie/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2012-09-06 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 17:58 Jimmy Tang [this message]
2012-09-06 18:19 ` issues with adjusting the crushmap in 0.51 Gregory Farnum
2012-09-06 18:51 ` Jimmy Tang
2012-09-06 20:31 ` Tommi Virtanen
2012-09-08 8:08 ` Jimmy Tang
2012-09-12 11:13 ` Jimmy Tang
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=20120906175821.GA32205@tchpc.tcd.ie \
--to=jtang@tchpc.tcd.ie \
--cc=ceph-devel@vger.kernel.org \
/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.