From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: all OSDs crash at more or less the same time
Date: Mon, 7 Mar 2016 00:37:59 +0100 [thread overview]
Message-ID: <56DCBF57.10008@digiware.nl> (raw)
Hi,
While running cephtool-test-rados.sh "all of a sudden" the OSDs
disapear, I had one of the logs open which contained at the end:
-2> 2016-03-06 21:56:02.073226 80569ed00 1 heartbeat_map is_healthy
'OSD::osd_op_tp thread 0x806795200' had timed out after 15
-1> 2016-03-06 21:56:02.073248 80569ed00 1 heartbeat_map is_healthy
'OSD::osd_op_tp thread 0x806795200' had suicide timed out after 150
0> 2016-03-06 21:56:02.113948 80569ed00 -1 common/HeartbeatMap.cc:
In function 'bool ceph::HeartbeatMap::_check(const ceph::heartbeat_handle_d
*, const char *, time_t)' thread 80569ed00 time 2016-03-06 21:56:02.073269
common/HeartbeatMap.cc: 86: FAILED assert(0 == "hit suicide timeout")
the monitor is still running. It claims the heartbeat_map is valid, but
still it suicides??
And what messages would prevent this from happening?
Receiving heartbeats from other OSDs?
IF so how would a 2 OSD server even survive when its connection would be
split for longer than 2,5 minute?
--WjW
next reply other threads:[~2016-03-06 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 23:37 Willem Jan Withagen [this message]
2016-03-07 11:08 ` all OSDs crash at more or less the same time Sage Weil
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=56DCBF57.10008@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
/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.