Hi
The issue is open: https://tracker.ceph.com/issues/64244
If you could take a look or let me know what are the next steps I would
be super grateful.
In the meantime I will try to increase the read throughput.
Thanks
Marc
On 1/26/24 15:23, Matt Benjamin wrote:
Hi Marc,
1. if you can,
Hi Marc,
1. if you can, yes, create a tracker issue on tracker.ceph.com?
2. you might be able to get more throughput with (some number) of
additional threads; the first thing I would try is prioritization (nice)
regards,
Matt
On Fri, Jan 26, 2024 at 6:08 AM Marc Singer wrote:
> Hi Matt
>
>
Hi Matt
Thanks for your answer.
Should I open a bug report then?
How would I be able to read more from it? Have multiple threads access
it and read from it simultaneously?
Marc
On 1/25/24 20:25, Matt Benjamin wrote:
Hi Marc,
No, the only thing you need to do with the Unix socket is to
Hi
I am using a unix socket client to connect with it and read the data
from it.
Do I need to do anything like signal the socket that this data has been
read? Or am I not reading fast enough and data is backing up?
What I am also noticing that at some point (probably after something
with
Hi Marc,
The ops log code is designed to discard data if the socket is
flow-controlled, iirc. Maybe we just need to handle the signal.
Of course, you should have something consuming data on the socket, but it's
still a problem if radosgw exits unexpectedly.
Matt
On Thu, Jan 25, 2024 at 10:08
