: 16 October 2015 00:50
> To: ceph-users@lists.ceph.com
> Subject: Re: [ceph-users] Cache Tiering Question
>
>
> Hello,
>
> Having run into this myself two days ago (setting relative sizing values
> doesn't
> flush things when expected) I'd say that the docu
On Fri, 16 Oct 2015, Robert LeBlanc wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Is the only option to restart the librbd client in this case? Anything
> I can do to help resolve it?
If you know which OSD the request is outstanding against (ceph daemon
objecter_requests) you c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Is the only option to restart the librbd client in this case? Anything
I can do to help resolve it?
Thanks,
-
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
On Fri, Oct 16, 2015 at 10:17 AM, Sage
On Fri, 16 Oct 2015, Robert LeBlanc wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I started another fio test to one of the same RBDs (leaving the hung
> ones still hung) and it is working OK, but the hungs ones are still
> just hung.
There is a full-disk failsafe that is still so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I started another fio test to one of the same RBDs (leaving the hung
ones still hung) and it is working OK, but the hungs ones are still
just hung.
-
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OK, I've set this up and now all I/O is locked up. I've reduced
target_max_bytes because one OSD was reporting 97% usage, there was
some I/O for a few seconds as things flushed, but client I/O is still
blocked. Anyone have some thoughts?
ceph osd cr
Hello,
Having run into this myself two days ago (setting relative sizing values
doesn't flush things when expected) I'd say that the documentation is
highly misleading when it comes to the relative settings.
And unclear when it comes to the size/object settings.
Guess this section needs at leas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks
-
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
On Thu, Oct 15, 2015 at 5:38 PM, JC Lopez wrote:
> Hi Robert
>
> usable bytes so before replication. The size of the actual original object
Hi Robert
usable bytes so before replication. The size of the actual original objects you
write.
Cheers
JC
> On 15 Oct 2015, at 16:33, Robert LeBlanc wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> One more question. Is max_{bytes,objects} before or after replication factor?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
One more question. Is max_{bytes,objects} before or after replication factor?
-
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
On Thu, Oct 15, 2015 at 4:42 PM, LOPEZ Jean-Charles wrote:
> Hi Robe
Hi Robert,
yes they do.
Pools don’t have a size when you create them hence the couple value/ratio that
is to be defined for cache tiering mechanism. Pool only have a number of PGs
assigned. So setting the max values and the ratios for dirty and full must be
set explicitly to match your configu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
hmmm...
http://docs.ceph.com/docs/master/rados/operations/cache-tiering/#relative-sizing
makes it sound like it should be based on the size of the pool and
that you don't have to set anything like max bytes/objects. Can you
confirm that cache_targe
> -Original Message-
> From: ceph-users [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of
> Robert LeBlanc
> Sent: 15 October 2015 22:06
> To: ceph-users@lists.ceph.com
> Subject: [ceph-users] Cache Tiering Question
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> ceph
I was not able to trigger eviction using percentage settings. I run
the hot pool into "cluster is full" and the eviction did not start. As
an option a threshold on # of objects did trigger an eviction.
Unfortunately it stalled all the writes to the hot pool until the
eviction was complete.
On Th
14 matches
Mail list logo
