Hello Casey,
Thanks a lot for that.
I’ve forgot to mention that in my previous message that I was able to trigger
the prefetch by header bytes=1-10
You can see the the read 1~10 in the osd logs I’ve sent here -
https://pastebin.com/nGQw4ugd
Which is wierd as it seems that it is not the same
that first "read 0~4194304" is probably what i fixed in
https://github.com/ceph/ceph/pull/53602, but it's hard to tell from
osd log where these osd ops are coming from. why are there several
[read 1~10] requests after that? the rgw log would be more useful for
debugging, with --debug-rgw=20 and
Hello Casey,
Thanks a lot for that.
I’ve forgot to mention that in my previous message that I was able to trigger
the prefetch by header bytes=1-10
You can see the the read 1~10 in the osd logs I’ve sent here -
https://pastebin.com/nGQw4ugd
Which is wierd as it seems that it is not the same
hey Ondrej,
thanks for creating the tracker issue
https://tracker.ceph.com/issues/62938. i added a comment there, and
opened a fix in https://github.com/ceph/ceph/pull/53602 for the only
issue i was able to identify
On Wed, Sep 20, 2023 at 9:20 PM Ondřej Kukla wrote:
>
> I was checking the
I was checking the tracker again and I found already fixed issue that seems to
be connected with this issue.
https://tracker.ceph.com/issues/44508
Here is the PR that fixes it https://github.com/ceph/ceph/pull/33807
What I’m still not understanding is why this is only happening when using
When checking the RGW logs I can confirm that it is in fact the same issue as
the one in the issue.
2023-09-20T12:52:06.670+ 7f216d702700 1 -- xxx.xxx.58.15:0/758879303 -->
[v2:xxx.xxx.58.2:6816/8556,v1:xxx.xxx.58.2:6817/8556] -- osd_op(unknown.0.0:238
18.651
I was checking the tracker again and I found already fixed issue that seems to
be connected with this issue.
https://tracker.ceph.com/issues/44508
Here is the PR that fixes it https://github.com/ceph/ceph/pull/33807
What I’m still not understanding is why this is only happening when using
