On Fri, Jul 10, 2015 at 10:45 PM, Deneau, Tom tom.den...@amd.com wrote:
I have an osd log file from an osd that hit a suicide timeout (with the
previous 1 events logged).
(On this node I have also seen this suicide timeout happen once before and
also a sync_entry timeout.
I can see
To: Deneau, Tom
Cc: ceph-devel
Subject: Re: osd suicide timeout
On Fri, Jul 10, 2015 at 10:45 PM, Deneau, Tom tom.den...@amd.com wrote:
I have an osd log file from an osd that hit a suicide timeout (with the
previous 1 events logged).
(On this node I have also seen this suicide timeout
[mailto:g...@gregs42.com]
Sent: Monday, July 13, 2015 5:07 AM
To: Deneau, Tom
Cc: ceph-devel
Subject: Re: osd suicide timeout
On Fri, Jul 10, 2015 at 10:45 PM, Deneau, Tom tom.den...@amd.com wrote:
I have an osd log file from an osd that hit a suicide timeout (with the
previous 1 events
-
From: Gregory Farnum [mailto:g...@gregs42.com]
Sent: Monday, July 13, 2015 11:45 AM
To: Deneau, Tom
Cc: ceph-devel
Subject: Re: osd suicide timeout
heartbeat_map reset_timeout 'OSD::osd_op_tp thread 0x3ff6eb0efd0' had suicide
timed out after 150
So that's the OSD's op thread, which
Subject: Re: osd suicide timeout
heartbeat_map reset_timeout 'OSD::osd_op_tp thread 0x3ff6eb0efd0' had suicide
timed out after 150
So that's the OSD's op thread, which is the one that does most of the work.
You often see the FileStore::op_tp when it's the disk or filesystem breaking,
but I do
I have an osd log file from an osd that hit a suicide timeout (with the
previous 1 events logged).
(On this node I have also seen this suicide timeout happen once before and also
a sync_entry timeout.
I can see that 6 minutes or so before that osd died, other osds on the same
node were
