Hi Trey,
If you run the upstream curl releases, please note that curl has a
poor security record and it's important to stay on top of updates.
https://curl.haxx.se/docs/security.html indicates that 7.44 has
security problems, and in fact there are eleven more security
announcements coming soon
(ht
Updating to libcurl 7.44 fixed the memory leak issue. Thanks for the tip,
Ben.
FWIW this was a massive memory leak, it rendered the system untenable in my
testing. RGW multisite will flat not work with the current CentOS/RHEL7
libcurl.
Seems like there are a lot of different problems caused b
Hi Ben,
I previously hit this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1327142
So I updated from libcurl 7.29.0-25 to the new update package libcurl
7.29.0-32 on RHEL 7, which fixed the deadlock problem.
I had not seen the issue you linked. It doesn't seem directly related,
since my p
What version of libcurl are you using?
I was hitting this bug with RHEL7/libcurl 7.29 which could also be your
catalyst.
http://tracker.ceph.com/issues/15915
Kind regards,
Ben Morrice
__
Ben Morrice | e: ben.morr...@epfl.ch |
I've been trying to test radosgw multisite and have a pretty bad memory
leak.It appears to be associated only with multisite sync.
Multisite works well for a small numbers of objects.However, it all
fell over when I wrote in 8M 64K objects to two buckets overnight for
testing (via cosbench
