Re: [ceph-users] pre-sharding s3 buckets

2018-06-29 Thread Sean Purdy
On Wed, 27 Jun 2018, Matthew Vernon said:
> Hi,
> 
> On 27/06/18 11:18, Thomas Bennett wrote:
> 
> > We have a particular use case that we know that we're going to be
> > writing lots of objects (up to 3 million) into a bucket. To take
> > advantage of sharding, I'm wanting to shard buckets, without the
> > performance hit of resharding.
> 
> I assume you're running Jewel (Luminous has dynamic resharding); you can
> set rgw_override_bucket_index_max_shards = X in your ceph.conf, which
> will cause all new buckets to have X shards for the indexes.
> 
> HTH,
> 
> Matthew

But watch out if you are running Luminous - manual and automatic
resharding breaks if you have versioning or lifecycles on your bucket.
Fix in next stable release 12.2.6 apparently.

http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-January/023968.html
http://tracker.ceph.com/issues/23886


Sean
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com


Re: [ceph-users] pre-sharding s3 buckets

2018-06-27 Thread Thomas Bennett
Hi Matthew,

Thanks for your reply, much appreciated.

Sorry, I meant to say that we're running on Luminous, so I'm aware of
dynamic resharding - however, I'm worried that this does not suit our
particular use case.

What I also forgot to mention is that we could be resharding a bucket 30
times in 8 hours as we will write ~3 million objects in ~8 hours.

Hence the idea that we should preshard to avoid any undesirable workloads.

Cheers,
Tom

On Wed, Jun 27, 2018 at 3:16 PM, Matthew Vernon  wrote:

> Hi,
>
> On 27/06/18 11:18, Thomas Bennett wrote:
>
> > We have a particular use case that we know that we're going to be
> > writing lots of objects (up to 3 million) into a bucket. To take
> > advantage of sharding, I'm wanting to shard buckets, without the
> > performance hit of resharding.
>
> I assume you're running Jewel (Luminous has dynamic resharding); you can
> set rgw_override_bucket_index_max_shards = X in your ceph.conf, which
> will cause all new buckets to have X shards for the indexes.
>
> HTH,
>
> Matthew
>
>
> --
>  The Wellcome Sanger Institute is operated by Genome Research
>  Limited, a charity registered in England with number 1021457 and a
>  company registered in England with number 2742969, whose registered
>  office is 215 Euston Road, London, NW1 2BE.
>



-- 
Thomas Bennett

SRAO
Storage Engineer - Science Data Processing
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com


[ceph-users] pre-sharding s3 buckets

2018-06-27 Thread Thomas Bennett
Hi,

We have a particular use case that we know that we're going to be writing
lots of objects (up to 3 million) into a bucket. To take advantage of
sharding, I'm wanting to shard buckets, without the performance hit of
resharding.

So far I've created an empty bucket and then used the radosgw-admin:

radosgw-admin bucket reshard --bucket test --num-shards 10

Is there another way to do this?

Or, is there a s3/ceph configuration option that will set the number of
shards when a bucket is created - with the hit that we might have buckets
with multiple empty shards, a sacrifice that I'm willing to take for the
convenience of it preconfigured.

Cheers,
Tom

-- 
Thomas Bennett

SRAO
Storage Engineer - Science Data Processing
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com