Hi Satoru, Unfortunately suspending versioning on a bucket prior to resharding does not work around this issue. Is it possible to stop client requests to the relevant bucket during resharding? Cory ________________________________ From: Satoru Takeuchi <satoru.takeuchi@xxxxxxxxx> Sent: Wednesday, June 14, 2023 11:42 PM To: Cory Snyder <csnyder@xxxxxxxxxxxxxxx> Cc: ceph-users@xxxxxxx <ceph-users@xxxxxxx>; Ceph Dev List <dev@xxxxxxx> Subject: Re: RGW versioned bucket index issues Hi Cory, > 1. PUT requests during reshard of versioned bucket fail with 404 and leave > behind dark data > > Tracker: https: //urldefense. com/v3/__https: //tracker. ceph. com/issues/61359__;!!J0dtj8f0ZRU!iYeliiauhqQFoQtyS_k_xXA3Bj6qrYRNunU-wxUE7QGYlRqXnxtPQ5WI4pf-HmrHUjI3vzDYBx2VvbO4FbYLABID-wMfIRo$ ZjQcmQRYFpfptBannerStart This Message Is From an Untrusted Sender You have not previously corresponded with this sender. <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/J0dtj8f0ZRU!gpOLoAmYo0w0NJ4yBJNe9Nv9-reakE7CSeulmGLok4g5wFW9L46Hw8_VUJqmXRt5XY-87NlMHullk5Pll6kNakV4Z2-Y0wAdQbNQUmOWK6gfHkzYHZjslAQF9plK6e_A$> Report Suspicious ZjQcmQRYFpfptBannerEnd Hi Cory, > 1. PUT requests during reshard of versioned bucket fail with 404 and leave > behind dark data > > Tracker: https://urldefense.com/v3/__https://tracker.ceph.com/issues/61359__;!!J0dtj8f0ZRU!iYeliiauhqQFoQtyS_k_xXA3Bj6qrYRNunU-wxUE7QGYlRqXnxtPQ5WI4pf-HmrHUjI3vzDYBx2VvbO4FbYLABID-wMfIRo$ Could you tell me whether this problem is bypassed by suspending(disabling) versioned buckets? I have some versioning buckets in my Ceph v17.2.6 clusters. These buckets need to be resharded to resolve large omap warnings caused by large index shard objects. This warning has existed for some months and the number of objects has been bigger and bigger. So I'd like to resolve this as soon as possible. In addition, if you have any other workaround, please let me know. Best, Satoru _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |