Hi,
On 06-05-17 20:08, Wido den Hollander wrote:
>> Op 6 mei 2017 om 9:55 schreef Christian Balzer :
>>
>>
>>
>> Hello,
>>
>> On Sat, 6 May 2017 09:25:15 +0200 (CEST) Wido den Hollander wrote:
>>
Op 5 mei 2017 om 10:33 schreef Sam Wouters :
Hi,
we have a small cluste
> Op 6 mei 2017 om 9:55 schreef Christian Balzer :
>
>
>
> Hello,
>
> On Sat, 6 May 2017 09:25:15 +0200 (CEST) Wido den Hollander wrote:
>
> > > Op 5 mei 2017 om 10:33 schreef Sam Wouters :
> > >
> > >
> > > Hi,
> > >
> > > we have a small cluster running on jewel 10.2.7; NL-SAS disks only
Hello,
On Sat, 6 May 2017 09:25:15 +0200 (CEST) Wido den Hollander wrote:
> > Op 5 mei 2017 om 10:33 schreef Sam Wouters :
> >
> >
> > Hi,
> >
> > we have a small cluster running on jewel 10.2.7; NL-SAS disks only, osd
> > data and journal co located on the disks; main purpose rgw secondary z
> Op 5 mei 2017 om 10:33 schreef Sam Wouters :
>
>
> Hi,
>
> we have a small cluster running on jewel 10.2.7; NL-SAS disks only, osd
> data and journal co located on the disks; main purpose rgw secondary zone.
>
> Since the upgrade to jewel, whenever a deep scrub starts on one of the
> rgw ind
Hi,
we have a small cluster running on jewel 10.2.7; NL-SAS disks only, osd
data and journal co located on the disks; main purpose rgw secondary zone.
Since the upgrade to jewel, whenever a deep scrub starts on one of the
rgw index pool pg's, slow requests start piling up and rgw requests are
blo