For mailing list archive readers in the future:
On Tue, Jul 9, 2019 at 1:22 PM Paul Emmerich wrote:
> Try to add "--inconsistent-index" (caution: will obviously leave your
> bucket in a broken state during the deletion, so don't try to use the
> bucket)
>
this was bad advice as long as
Created https://tracker.ceph.com/issues/40700 (sry forgot to mention).
On 11.07.19 16:41, Matt Benjamin wrote:
I don't think one has been created yet. Eric Ivancich and Mark Kogan
of my team are investigating this behavior.
Matt
On Thu, Jul 11, 2019 at 10:40 AM Paul Emmerich wrote:
Is
On 11/07/2019 15:40, Paul Emmerich wrote:
Is there already a tracker issue?
I'm seeing the same problem here. Started deletion of a bucket with a
few hundred million objects a week ago or so and I've now noticed that
it's also leaking memory and probably going to crash.
Going to investigate
I don't think one has been created yet. Eric Ivancich and Mark Kogan
of my team are investigating this behavior.
Matt
On Thu, Jul 11, 2019 at 10:40 AM Paul Emmerich wrote:
>
> Is there already a tracker issue?
>
> I'm seeing the same problem here. Started deletion of a bucket with a few
>
Is there already a tracker issue?
I'm seeing the same problem here. Started deletion of a bucket with a few
hundred million objects a week ago or so and I've now noticed that it's
also leaking memory and probably going to crash.
Going to investigate this further...
Paul
--
Paul Emmerich
Hi Harald,
Please file a tracker issue, yes. (Deletes do tend to be slower,
presumably due to rocksdb compaction.)
Matt
On Tue, Jul 9, 2019 at 7:12 AM Harald Staub wrote:
>
> Currently removing a bucket with a lot of objects:
> radosgw-admin bucket rm --bucket=$BUCKET --bypass-gc
Try to add "--inconsistent-index" (caution: will obviously leave your
bucket in a broken state during the deletion, so don't try to use the
bucket)
You can also speed up the deletion with "--max-concurrent-ios" (default
32). The documentation incorrectly claims that "--max-concurrent-ios" is
only
Currently removing a bucket with a lot of objects:
radosgw-admin bucket rm --bucket=$BUCKET --bypass-gc --purge-objects
This process was killed by the out-of-memory killer. Then looking at the
graphs, we see a continuous increase of memory usage for this process,
about +24 GB per day. Removal
