All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Dan Van Der Ster <daniel.vanderster@cern.ch>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Stopping ceph daemons during the upgrade
Date: Mon, 18 Aug 2014 18:00:00 +0200	[thread overview]
Message-ID: <53F22300.6080702@dachary.org> (raw)
In-Reply-To: <A856D71F-CC6F-4A6A-B29B-FD19FB511482@cern.ch>

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

Hi Dan,

Pre-loading the erasure code plugins will reduce this race condition (i.e. the files will have to be modified between the start of the ceph-osd process and the bootstrap phase where it loads the plugins for it to happen) and it seems to be preferable to stopping the daemons. Thanks for giving an additional incentive to go in this direction !

Cheers

On 18/08/2014 17:31, Dan Van Der Ster wrote:
> Hi,
> 
> On 18 Aug 2014, at 17:19, Loic Dachary <loic@dachary.org> wrote:
> 
>> there probably is a way to do something similar with RPM packages. 
> 
> That behaviour (well, close enough) just _removed_ from firefly, see:
>   https://github.com/ceph/ceph/commit/361c1f8554ce1fedfd0020cd306c41b0ba25f53e
> 
> I don’t have a strong opinion if the pkg update should restart the daemon or not — but we should try not to change this too often as it changes our operating procedures.
> 
> Cheers, Dan--
> 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
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2014-08-18 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 15:19 Stopping ceph daemons during the upgrade Loic Dachary
2014-08-18 15:31 ` Dan Van Der Ster
2014-08-18 16:00   ` Loic Dachary [this message]
2014-08-18 16:08     ` Sage Weil
2014-08-18 16:24       ` Loic Dachary

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=53F22300.6080702@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=daniel.vanderster@cern.ch \
    /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.