All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Zafman <dzafman@redhat.com>
To: "Podoski, Igor" <Igor.Podoski@ts.fujitsu.com>,
	"Deneau, Tom" <tom.deneau@amd.com>,
	"\"Dałek, Piotr\"" <Piotr.Dalek@ts.fujitsu.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: deleting objects from a pool
Date: Fri, 26 Jun 2015 08:21:22 -0700	[thread overview]
Message-ID: <558D6DF2.5070302@redhat.com> (raw)
In-Reply-To: <66EBB02ADA308B4F8273E99FC000126C6BEA0BDEFE@ABGEX70E.FSC.NET>


This is a dangerous command because it can remove all your objects. At 
least it can only do one namespace at a time.  It was intended to 
cleanup rados bench runs, and is dangerous because it doesn't require 
extra hoops like rados rmpool does.

I'm tempted to disallow a usage this way with empty --prefix/--run-name 
arguments.

David

On 6/25/15 10:40 PM, Podoski, Igor wrote:
> Hi David,
>
> You're right, now I see adding --run-name "" will clean all benchmark data from specified namespace, so you can run command only once.
>
> rados -p <poolname> -N <namespace> cleanup --prefix "" --run-name ""
>
> Regards,
> Igor.
>
>
> -----Original Message-----
> From: David Zafman [mailto:dzafman@redhat.com]
> Sent: Friday, June 26, 2015 3:46 AM
> To: Podoski, Igor; Deneau, Tom; Dałek, Piotr; ceph-devel
> Subject: Re: deleting objects from a pool
>
>
> If you have rados bench data around, you'll need to run cleanup a second time because the first time the "benchmark_last_metadata" object will be consulted to find what objects to remove.
>
> Also, using cleanup this way will only remove objects from the default namespace unless a namespace is specified with the -N option.
>
> rados -p <poolname> -N <namespace> cleanup --prefix ""
>
> David
>
> On 6/24/15 11:06 PM, Podoski, Igor wrote:
>> Hi,
>>
>> It appears, that cleanup can be used as a purge:
>>
>> rados -p <poolname> cleanup  --prefix ""
>>
>> Regards,
>> Igor.
>>
>>
>> -----Original Message-----
>> From: ceph-devel-owner@vger.kernel.org
>> [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Deneau, Tom
>> Sent: Wednesday, June 24, 2015 10:22 PM
>> To: Dałek, Piotr; ceph-devel
>> Subject: RE: deleting objects from a pool
>>
>> I've noticed that deleting objects from a basic k=2 m=1 erasure pool is much much slower than deleting a similar number of objects from a replicated size 3 pool (so the same number of files to be deleted).   It looked like the ec pool object deletion was almost 20x slower.  Is there a lot more work to be done to delete an ec pool object?
>>
>> -- Tom
>>
>>
>>
>>> -----Original Message-----
>>> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-
>>> owner@vger.kernel.org] On Behalf Of Dalek, Piotr
>>> Sent: Wednesday, June 24, 2015 11:56 AM
>>> To: ceph-devel
>>> Subject: Re: deleting objects from a pool
>>>
>>>> -----Original Message-----
>>>> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-
>>>> owner@vger.kernel.org] On Behalf Of Deneau, Tom
>>>> Sent: Wednesday, June 24, 2015 6:44 PM
>>>>
>>>> I have benchmarking situations where I want to leave a pool around
>>>> but delete a lot of objects from the pool.  Is there any really fast
>>>> way to do
>>> that?
>>>> I noticed rados rmpool is fast but I don't want to remove the pool.
>>>>
>>>> I have been spawning multiple threads, each deleting a subset of the
>>> objects
>>>> (which I believe is what rados bench write does) but even that can
>>>> be very slow.
>>> For now, apart from "rados -p <poolname> cleanup" (which doesn't
>>> purge the pool, but merely removes objects written during last
>>> benchmark run), the only option is by brute force:
>>>
>>> for i in $(rados -p <poolname> ls); do (rados -p <poolname> rm $i
>>> &>/dev/null &); done;
>>>
>>> There's no "purge pool" command in rados -- not yet, at least. I was
>>> thinking about one, but never really had time to implement one.
>>>
>>> With best regards / Pozdrawiam
>>> Piotr Dałek
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
>>> in the body of a message to majordomo@vger.kernel.org More majordomo
>>> info at  http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
>> in the body of a message to majordomo@vger.kernel.org More majordomo
>> info at  http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
>> in the body of a message to majordomo@vger.kernel.org More majordomo
>> info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-06-26 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 16:43 deleting objects from a pool Deneau, Tom
2015-06-24 16:55 ` Dałek, Piotr
2015-06-24 20:22   ` Deneau, Tom
2015-06-25  6:06     ` Podoski, Igor
2015-06-25 15:40       ` Deneau, Tom
2015-06-26  1:45       ` David Zafman
2015-06-26  5:40         ` Podoski, Igor
2015-06-26 15:21           ` David Zafman [this message]
2015-06-29  6:19             ` Dałek, Piotr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=558D6DF2.5070302@redhat.com \
    --to=dzafman@redhat.com \
    --cc=Igor.Podoski@ts.fujitsu.com \
    --cc=Piotr.Dalek@ts.fujitsu.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=tom.deneau@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.