CEPH filesystem development
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: Nathan Cutler <ncutler@suse.cz>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Would it make sense to require ntp
Date: Fri, 6 Nov 2015 12:36:36 +0100	[thread overview]
Message-ID: <563C90C4.6090202@42on.com> (raw)
In-Reply-To: <563C7BB1.7030500@suse.cz>

On 11/06/2015 11:06 AM, Nathan Cutler wrote:
> Hi Ceph:
> 
> Recently I encountered some a "clock skew" issue with 0.94.3. I have
> some small demo clusters in AWS. When I boot them up, in most cases the
> cluster will start in HEALTH_WARN due to clock skew on some of the MONs.
> 
> I surmise that this is due to a race condition between the ceph-mon and
> ntpd systemd services. Sometimes ntpd.service starts *after* ceph-mon -
> in this case the MON sees a wrong/unsynchronized time value.
> 
> Now, even though ntpd.service starts (and fixes the time value) very
> soon afterwards, the cluster remains in clock skew for a long time - but
> that is a separate issue. What I would like to ask is this:
> 
> Is there any reasonable Ceph cluster node configuration that does not
> include running the NTP daemon?
> 

Well, the MONs are very, very time sensitive. OSDs somewhat less, but if
they drift too far they run into trouble authenticating.

> If the answer is "no", would it make sense to make NTP a runtime
> dependency and tell the ceph-mon systemd service to wait for
> ntpd.service before it starts?
> 

I think it makes sense, correct time is essential imho.

> Thanks and regards
> 


-- 
Wido den Hollander
42on B.V.
Ceph trainer and consultant

Phone: +31 (0)20 700 9902
Skype: contact42on

  reply	other threads:[~2015-11-06 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 10:06 Would it make sense to require ntp Nathan Cutler
2015-11-06 11:36 ` Wido den Hollander [this message]
2015-11-06 12:26 ` John Spray
2015-11-06 15:08   ` Gregory Farnum
2015-11-06 15:19     ` Vasiliy Angapov
2015-11-06 17:44   ` Jeremy Hanmer
2016-01-21  2:45   ` Dan Mick

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=563C90C4.6090202@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ncutler@suse.cz \
    /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