Hi Yuval,
Thanks for having a look at bucket notifications and collecting
feedback. I also see potential for improvement in the area of bucket
notifications.
We have observed issues in a setup with Rabbit MQ as a broker where the
RADOS queue seems to fill up and cients receive "slow down" re
Hi,
I noticed that the error behavior is actually depending on the length of
the PutObject request. The subsequent request
* results in a 400 Bad Request error (with log message "failed to read
header: bad method") for small files or
* a read timeout on the connection is encountered by the clie
Hi,
When I try to upload an object to a non-existing bucket, PutObject
returns a 404 Not Found with error code NoSuchBucket as expected.
Trying to create the bucket afterwards however results in a 400 Bad
Request error which is not expected. The rgw logs indicate "failed to
read header: bad
Hi Yuval,
Both fixes are now under review;
https://github.com/ceph/ceph/pull/48875
https://github.com/ceph/ceph/pull/48877
it might take a little longer, but the fixes should also be backported to
quincy.
great, thanks for the quick fix!
=Stefan
_
Hi Yuval,
On 11/13/22 10:24, Yuval Lifshitz wrote:
The issue was indeed fixed (both with regard to filtering and sending the
metadata) in the tracker that you mentioned but was broken by another fix
It seems something similar happend to your fix for "notifications: zero
timestamp in complete
