That did the trick, we had it set to 0 just on the swift rgw definitions
although it was set on other rgw services, I'm guessing someone must have
thought there was a different precedence in play in the past.
On Tue, 2018-12-11 at 11:41 -0500, Casey Bodley wrote:
Hi Leon,
Are you running with
Hi Leon,
Are you running with a non-default value of rgw_gc_max_objs? I was able
to reproduce this exact stack trace by setting rgw_gc_max_objs = 0; I
can't think of any other way to get a 'Floating point exception' here.
On 12/11/18 10:31 AM, Leon Robinson wrote:
Hello, I have found a suref
Hello, I have found a surefire way to bring down our swift gateways.
First, upload a bunch of large files and split it in to segments, e.g.
for i in {1..100}; do swift upload test_container -S 10485760
CentOS-7-x86_64-GenericCloud.qcow2 --object-name
CentOS-7-x86_64-GenericCloud.qcow2-$i; done
