From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Tommi Virtanen <tv@inktank.com>
Cc: Samuel Just <sam.just@inktank.com>,
Gregory Farnum <greg@inktank.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: domino-style OSD crash
Date: Tue, 10 Jul 2012 19:36:01 +0200 [thread overview]
Message-ID: <4FFC6801.40509@univ-nantes.fr> (raw)
In-Reply-To: <CADvuQRGLNfJ5UXMSR141z8Hd3Y7x+vCeZknruCJKE3g4rYrmLw@mail.gmail.com>
Le 10/07/2012 19:11, Tommi Virtanen a écrit :
> On Tue, Jul 10, 2012 at 9:39 AM, Yann Dupont <Yann.Dupont@univ-nantes.fr> wrote:
>>> The cluster mechanism was never intended for moving existing osds to
>>> other clusters. Trying that might not be a good idea.
>> Ok, good to know. I saw that the remaining maps could lead to problem, but
>> in 2 words, what are the other associated risks ? Basically If I use 2
>> distincts config files,
>> with differents & non-overlapping paths, and different ports for OSD, MDS &
>> MON, we basically have 2 distincts and independant instances ?
> Fundamentally, it comes down to this: the two clusters will still have
> the same fsid, and you won't be isolated from configuration errors or
Ah I understand. This is not the case : see :
root@chichibu:~# cat /CEPH/data/osd.0/fsid
f00139fe-478e-4c50-80e2-f7cb359100d4
root@chichibu:~# cat /CEPH-PROD/data/osd.0/fsid
43afd025-330e-4aa8-9324-3e9b0afce794
(CEPH-PROD is the old btrfs volume ). /CEPH is new xfs volume,
completely redone & reformatted with mkcephfs. The volumes are totally
independant :
if you want the gore details :
root@chichibu:~# lvs
LV VG Attr LSize Origin Snap% Move Log
Copy% Convert
ceph-osd LocalDisk -wi-a- 225,00g
mon-btrfs LocalDisk -wi-ao 10,00g
mon-xfs LocalDisk -wi-ao 10,00g
data ceph-chichibu -wi-ao 5,00t <- OLD btrfs,
mounted on /CEPH-PROD
data xceph-chichibu -wi-ao 4,50t <- NEW xfs, mounted
on /CEPH
> leftover state (such as the monmap) in any way. There's a high chance
> that your "let's poke around and debug" cluster wrecks your healthy
> cluster.
Yes I understand the risk.
>> By the way, is using 2 mon instance with different ports supported ?
> Monitors are identified by ip:port. You can have multiple bind to the
> same IP address, as long as they get separate ports.
>
> Naturally, this practically means giving up on high availability.
The idea is not just having 2 mon. I'll still use 3 differents machines
for mon, but with 2 mon instance on each. One for the current ceph, the
other for the old ceph.
2x3 Mon.
Cheers,
--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@univ-nantes.fr
--
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-07-10 17:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 8:44 domino-style OSD crash Yann Dupont
2012-06-04 16:16 ` Tommi Virtanen
2012-06-04 17:40 ` Sam Just
2012-06-04 18:34 ` Greg Farnum
2012-07-03 8:40 ` Yann Dupont
2012-07-03 19:42 ` Tommi Virtanen
2012-07-03 20:54 ` Yann Dupont
2012-07-03 21:38 ` Tommi Virtanen
2012-07-04 8:06 ` Yann Dupont
2012-07-04 16:21 ` Gregory Farnum
2012-07-04 17:53 ` Yann Dupont
2012-07-05 21:32 ` Gregory Farnum
2012-07-06 7:19 ` Yann Dupont
2012-07-06 17:01 ` Gregory Farnum
2012-07-07 8:19 ` Yann Dupont
2012-07-09 17:14 ` Samuel Just
2012-07-10 9:46 ` Yann Dupont
2012-07-10 15:56 ` Tommi Virtanen
2012-07-10 16:39 ` Yann Dupont
2012-07-10 17:11 ` Tommi Virtanen
2012-07-10 17:36 ` Yann Dupont [this message]
2012-07-10 18:16 ` Tommi Virtanen
2012-07-09 17:43 ` Tommi Virtanen
2012-07-09 19:05 ` Yann Dupont
2012-07-09 19:48 ` Tommi Virtanen
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=4FFC6801.40509@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=sam.just@inktank.com \
--cc=tv@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.