From: Wido den Hollander <wido@42on.com>
To: Sage Weil <sage@newdream.net>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: pre_start command not executed with upstart
Date: Thu, 30 Jul 2015 09:43:33 +0200 [thread overview]
Message-ID: <55B9D5A5.9060301@42on.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1507280528210.22099@cobra.newdream.net>
On 28-07-15 14:29, Sage Weil wrote:
> On Tue, 28 Jul 2015, Wido den Hollander wrote:
>> Hi,
>>
>> I was trying to inject a pre_start command on a bunch of OSDs under
>> Ubuntu 14.04, but that didn't work.
>>
>> I found out that only the sysvinit script execute pre_start commands,
>> but the upstart nor the systemd scripts do this.
>>
>> Is this a thing which will disappear or is this just a oversight?
>>
>> I'm actually using "sleep 30" as a pre-start to prevent all OSDs from
>> starting at the same time. Big boxes which die under the workload of all
>> OSDs starting at the same time.
>>
>> I also try to prevent a lot of OSDMap changes by booting the OSDs slowly
>> so I tried to fix this with "pre_start".
>
> I was hoping to let it die...
>
> I would take a fresh look at systemd and see if there is a
> different/better mechanism there to address the startup issue. You can
> manually add a prestart script/command to the unit file...
>
Oh, it doesn't matter if it dies out. It's just that there will probably
be scenarios where users want to do some sort of pre-start before a OSD
is executed.
The update_crush hook is one of the examples which is already executed
for example.
A pre_start which does a mount for example (for those without udev)
might be useful.
Wido
> sage
>
next prev parent reply other threads:[~2015-07-30 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 7:55 pre_start command not executed with upstart Wido den Hollander
2015-07-28 8:52 ` Gregory Farnum
2015-07-28 12:29 ` Sage Weil
2015-07-30 7:43 ` Wido den Hollander [this message]
2015-07-30 12:28 ` Sage Weil
2015-07-30 12:30 ` Wido den Hollander
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=55B9D5A5.9060301@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.