From: Robert LeBlanc <robert@leblancnet.us>
To: Stefan Kooman <stefan@bit.nl>
Cc: ceph-devel <ceph-devel@vger.kernel.org>, ceph-users <ceph-users@ceph.io>
Subject: Re: [ceph-users] Re: Nautilus 14.2.19 mon 100% CPU
Date: Fri, 9 Apr 2021 10:41:09 -0600 [thread overview]
Message-ID: <CAANLjFpKGaKRM+2j6+YfLsufdgQi3jz_Nm5RNsSpbVGmSsFj5g@mail.gmail.com> (raw)
In-Reply-To: <8933c3a0-64f7-aaab-6ab7-30e39b76a387@bit.nl>
On Fri, Apr 9, 2021 at 9:25 AM Stefan Kooman <stefan@bit.nl> wrote:
> Are you running with 1 mon now? Have you tried adding mons from scratch?
> So with a fresh database? And then maybe after they have joined, kill
> the donor mon and start from scratch.
>
> You have for sure not missed a step during the upgrade (just checking
> mode), i.e. ceph osd require-osd-release nautilus.
I have tried adding one of the other monitors by removing the data
directory and starting from scratch, but it would go back to the
monitor elections and I didn't feel comfortable that it's up to sync
to fail over to it so I took it back out. I have run `ceph
osd-require-osd-release nautilus` after the upgrade of all the OSDs.
I'll go back and double check all the steps, but I think I got them
all.
Thank you,
Robert LeBlanc
next prev parent reply other threads:[~2021-04-09 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAANLjFpjRLtV+GR4WV15iXXCvkig6tJAr_G=_bZpZ=jKnYfvTQ@mail.gmail.com>
2021-04-08 17:24 ` Nautilus 14.2.19 mon 100% CPU Robert LeBlanc
2021-04-08 19:11 ` [ceph-users] " Stefan Kooman
2021-04-08 20:26 ` Robert LeBlanc
[not found] ` <CAKTRiELqxD+0LtRXan9gMzot3y4A4M4x=km-MB2aET6wP_5mQg@mail.gmail.com>
2021-04-09 3:48 ` Robert LeBlanc
2021-04-09 13:40 ` Robert LeBlanc
2021-04-09 15:25 ` [ceph-users] " Stefan Kooman
2021-04-09 16:41 ` Robert LeBlanc [this message]
2021-04-09 17:01 ` Robert LeBlanc
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=CAANLjFpKGaKRM+2j6+YfLsufdgQi3jz_Nm5RNsSpbVGmSsFj5g@mail.gmail.com \
--to=robert@leblancnet.us \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.io \
--cc=stefan@bit.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).