Seems like this sharding we need to be plan carefully since the beginning. I'm thinking to set the shard number by default to the maximum which is 64k and leave it as is so we will never reach the limit only if we reach the maximum number of objects. Would be interesting to know what is the side effect if I set the shards to 64k by default. Istvan Szabo Senior Infrastructure Engineer --------------------------------------------------- Agoda Services Co., Ltd. e: istvan.szabo@xxxxxxxxx --------------------------------------------------- -----Original Message----- From: Timothy Geier <tgeier@xxxxxxxxxxxxx> Sent: Saturday, November 21, 2020 12:22 AM To: Eric Ivancich <ivancich@xxxxxxxxxx>; ceph-users <ceph-users@xxxxxxx> Subject: [Suspicious newsletter] Re: Unable to reshard bucket Email received from outside the company. If in doubt don't click links nor open attachments! ________________________________ On Thu, 2020-11-19 at 13:38 -0500, Eric Ivancich wrote: > Hey Timothy, > > Did you ever resolve this issue, and if so, how? Unfortunately, I was never able to resolve it; the bucket(s) in question had to be recreated and then removed. > > > Thank you..I looked through both logs and noticed this in the cancel > > one: > > > > osd_op(unknown.0.0:4164 41.2 > > 41:55b0279d:reshard::reshard.0000000009:head [call > > rgw.reshard_remove] snapc 0=[] ondisk+write+known_if_redirected > > e24984) v8 -- > > 0x7fe9b3625710 con 0 > > osd_op_reply(4164 reshard.0000000009 [call] v24984'105796943 > > uv105796922 ondisk = -2 > > ((2) No such file or directory)) v8 ==== 162+0+0 (203651653 0 0) > > 0x7fe9880044a0 con > > 0x7fe9b3625b70 > > ERROR: failed to remove entry from reshard log, > > oid=reshard.0000000009 tenant= bucket=foo > > > > Is there anything else that I should look for? It looks like the > > cancel process thinks that reshard.0000000009 is present (and > > probably blocking my attempts at resharding) but it's not actually > > there and thus can't be removed. > > Eric > -- > J. Eric Ivancich > he / him / his > Red Hat Storage > Ann Arbor, Michigan, USA > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |