Hi,
I have a Ceph cluster with 6 hosts and 24 OSDs (mon and rgw colocated on these
hosts) that is used just for RGW. Since upgrading to from Kraken (11.2.0) to
Luminous (12.2.0) a week ago I can see lots of IOPS in the default.rgw.gc pool.
The cluster was created with Kraken two months ago and
s: bytes
Content-Type: application/xml
Date: Sat, 11 Feb 2017 14:48:46 GMT
Connection: close
NotImplementedtx1f1ec-00589f244e-6f2baa-default6f2baa-default-default
Uwe
> Am 10.02.2017 um 20:40 schrieb Robin H. Johnson :
>
> On Fri, Feb 10, 2017 at 05:14:51PM +0100, Uwe Mese
Hey,
just to keep you updated: I was able to add a lifecycle using s3cmd (version
1.6.1). I think I can live with that because for me changing lifecycles is some
one-time setup task.
Uwe
> Am 10.02.2017 um 01:32 schrieb Uwe Mesecke :
>
> Hey,
>
> I am trying to do some testi
Hey,
I am trying to do some testing of S3 bucket lifecycles in Kraken but I am
unable to setup a lifecycle. RGW always returns "501 Not Implemented“.
>>>
PUT /pdtest_expire_test?lifecycle HTTP/1.1
[…]
http://s3.amazonaws.com/doc/2006-03-01/";>testEnabled1
>>>
<<<
HTTP/1.1 501 Not Implemented
[
Hi David,
> Am 06.06.2016 um 15:26 schrieb David Turner :
>
> Best practices in general say to do them separate. If something doesn't
> work... Is it the new kernel, some package that are different on 16.04,
> Jewel, etc. The less things in that list the easier it is to track down the
> issue
sds for a particular pg from when it is clean until it
>>>>> develops an unfound object.
>>>>> -Sam
>>>>>
>>>>> On Wed, Jun 1, 2016 at 5:36 AM, Diego Castro
>>>>> wrote:
>>>>>> Hello Uwe, i also have sortbitwise
> Am 01.06.2016 um 10:25 schrieb Diego Castro :
>
> Hello, i have a cluster running Jewel 10.2.0, 25 OSD's + 4 Mon.
> Today my cluster suddenly went unhealth with lots of stuck pg's due unfound
> objects, no disks failures nor node crashes, it just went bad.
>
> I managed to put the cluster on
