On 10/31/2012 12:02 PM, Matt Weil wrote:
I have a system with a bunch or ram that I want to remain the active MDS
but still have a backup.
This config doesn't seem to be working. I can make linuscs92 the active
by stopping and starting the mds on linuscs95. It would be nice for
linuscs92 to be the active from the start.
[mds.linuscs95]
host = linuscs95
mds standby replay = true
mds standby for name = linuscs92
Hi Matt,
Can you post your ceph config? Once you startup your ceph cluster, you
see that linuscs92 is the standby and linuscs95 is the active? How are
you starting your cluster?
Also about disk write cache.
If the Data center, servers and storage units are backed by redundant
power sources, Batteries and a generator. Is the concern for data loss
less?
Yes, if you have that setup you can enable the disk cache and be
reasonably assured that a power failure of a single component won't
cause a loss of data.
Any one turn disk write cache on and see a great improvement?
This is dependent on your hardware. If you have raid controllers with
battery backed cache, enabling/disabling the disk caches probably won't
make much of a difference to performance. Rather than speculate though,
I would encourage you to benchmark it using Jens Axboe's fio benchmark:
cat > write.fio -<<EOF
[randwrite]
rw=randw
size=128m
direct=1
[write]
rw=write
size=1024m
direct=1
EOF
# enable cache
hdparm -W 1 /dev/sdX
# test with cache
fio write.fio
# disable cache
hdparm -W 0 /dev/sdX
# test without cache
fio write.fio
compare the output of the two fio benchmarks. Don't forget to return
the disk cache to its previously enabled/disabled state!
-sam
Thanks
Matt
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
