I am experimenting with RGW bucket notifications and the simple https endpoint.
I have it mostly working expect for the concept of telling RGW that I have received the notification. If I set persistent = False when I issue a put from an s3 compatible client the command “hangs” as I think that RGW is waiting for an ack from the notification event it has just sent. In this test case I am specifying a simple https endpoint. I am thinking that I need to “ack back” so that RGW tell the client that the request is complete. In async mode, RGW keep hammering my endpoint with notifications. I image it will not stop until it gets an ack. How do you send acks back to RGW when you are using simple https notification endpoints? Thanks! -- Mark Selby Sr Linux Administrator, The Voleon Group mse...@voleon.com This email is subject to important conditions and disclosures that are listed on this web page: https://voleon.com/disclaimer/.
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
