On 6-11-2017 14:05, Chris Jones wrote:
> I'll document the resolution here for anyone else who experiences
> similar issues.
>
> We have determined the root cause of the long boot time was a
> combination of factors having to do with ZFS version and tuning, in
> combination with how long filenames
esday, November 1, 2017 4:51:52 PM
To: Chris Jones; Gregory Farnum
Cc: ceph-users@lists.ceph.com
Subject: Re: [ceph-users] Hammer to Jewel Upgrade - Extreme OSD Boot Time
On 01/11/2017 18:04, Chris Jones wrote:
> Greg,
>
> Thanks so much for the reply!
>
> We are not clear on why ZFS is b
sedtomakealivingmanpickintheban_0e6d86f58e03d0f6de04_0_long",
"user.cephos.lfn3-alt", 0x7fd4e8017680, 1024) = -1 ENODATA (No data
available) <0.18>
--
Christopher J. Jones
-----------------
phos.lfn3-alt", 0x7fd4e8017680, 1024) = -1 ENODATA (No data available)
<0.18>
--
Christopher J. Jones
________________
From: Gregory Farnum
Sent: Monday, October 30, 2017 6:20:15 PM
To: Chris Jones
Cc: ceph-users@lists.ceph.com
Subje
On Thu, Oct 26, 2017 at 11:33 AM Chris Jones wrote:
> The long running functionality appears to be related to clear_temp_objects();
> from OSD.cc called from init().
>
>
> What is this functionality intended to do? Is it required to be run on
> every OSD startup? Any configuration settings that w
The long running functionality appears to be related to clear_temp_objects();
from OSD.cc called from init().
What is this functionality intended to do? Is it required to be run on every
OSD startup? Any configuration settings that would help speed this up?
---
After upgrading from CEPH Hammer to Jewel, we are experiencing extremely long
osd boot duration.
This long boot time is a huge concern for us and are looking for insight into
how we can speed up the boot time.
In Hammer, OSD boot time was approx 3 minutes. After upgrading to Jewel, boot
time i
