All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Eduardo Luis <joao.luis@inktank.com>
To: James Harper <james.harper@bendigoit.com.au>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: documentation error for adding monitor?
Date: Mon, 06 Jan 2014 16:35:47 +0000	[thread overview]
Message-ID: <52CADB63.6090301@inktank.com> (raw)
In-Reply-To: <6035A0D088A63A46850C3988ED045A4B6F359EEA@BITCOM1.int.sbss.com.au>

On 01/05/2014 10:31 PM, James Harper wrote:
> When I follow the steps for adding a new monitor at http://ceph.com/docs/master/rados/operations/add-or-rm-mons/, the 'ceph mon add <mon-id> <ip[:port>' step always tells me that the monitor already exists. Is this step actually necessary?
>
> Thanks
>
> James

Well, this is an annoying bug we just haven't been out to fix it.

In a nutshell, when you issue the add command we queue the command 
message until the monitor is actually added to the monmap -- which makes 
sense, as we don't want to return success before it actually happens. 
However, the monitor will bootstrap once it gets a new monmap, recalc 
the ranks and trigger a new election -- and this happens before the 
message is replied to.  Once the election is over, the monitor will 
rerun any queued messages it may have, so that it may forward those 
messages to the new leader (if any) or handle any message that whose 
actions may have been interrupted by the election -- and the message we 
queued earlier ends up being rerun, thus the error: when that message is 
rerun, the monitor it is trying to add already exists.

The monitor was successfully added though.

   -Joao


-- 
Joao Eduardo Luis
Software Engineer | http://inktank.com | http://ceph.com

      reply	other threads:[~2014-01-06 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 22:31 documentation error for adding monitor? James Harper
2014-01-06 16:35 ` Joao Eduardo Luis [this message]

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=52CADB63.6090301@inktank.com \
    --to=joao.luis@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=james.harper@bendigoit.com.au \
    /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.