Hi,
after renaming our Ceph Luminous cluster (which we use with RGW), we're
unable to get objects stored in RGW via S3 API (classic HTTP get works).
We were migrating cluster from one datacenter to another and by doing
so, we needed to completely rename hostnames of nodes and also change IP
a
Hi,
I used https://github.com/dvassallo/s3-benchmark to measure some
> performance values for the rgws and got some unexpected results.
> Everything above 64K has excellent performance but below it drops down to
> a fraction of the speed and responsiveness resulting in even 256K objects
> being fa
Florian,
Thanks for posting about this issue. This is something that we have
been experiencing (stale exclusive locks) with our OpenStack and Ceph
cloud more frequently as our datacentre has had some reliability
issues recently with power and cooling causing several unexpected
shutdowns.
At this
On Tue, Nov 19, 2019 at 1:51 PM shubjero wrote:
>
> Florian,
>
> Thanks for posting about this issue. This is something that we have
> been experiencing (stale exclusive locks) with our OpenStack and Ceph
> cloud more frequently as our datacentre has had some reliability
> issues recently with pow
On 19/11/2019 20:03, Jason Dillaman wrote:
> On Tue, Nov 19, 2019 at 1:51 PM shubjero wrote:
>>
>> Florian,
>>
>> Thanks for posting about this issue. This is something that we have
>> been experiencing (stale exclusive locks) with our OpenStack and Ceph
>> cloud more frequently as our datacentre
On Tue, Nov 19, 2019 at 2:49 PM Florian Haas wrote:
>
> On 19/11/2019 20:03, Jason Dillaman wrote:
> > On Tue, Nov 19, 2019 at 1:51 PM shubjero wrote:
> >>
> >> Florian,
> >>
> >> Thanks for posting about this issue. This is something that we have
> >> been experiencing (stale exclusive locks) wi
On 19/11/2019 21:32, Jason Dillaman wrote:
>> What, exactly, is the "reasonably configured hypervisor" here, in other
>> words, what is it that grabs and releases this lock? It's evidently not
>> Nova that does this, but is it libvirt, or Qemu/KVM, and if so, what
>> magic in there makes this happe
On Tue, Nov 19, 2019 at 4:09 PM Florian Haas wrote:
>
> On 19/11/2019 21:32, Jason Dillaman wrote:
> >> What, exactly, is the "reasonably configured hypervisor" here, in other
> >> words, what is it that grabs and releases this lock? It's evidently not
> >> Nova that does this, but is it libvirt,
On 19/11/2019 22:19, Jason Dillaman wrote:
> On Tue, Nov 19, 2019 at 4:09 PM Florian Haas wrote:
>>
>> On 19/11/2019 21:32, Jason Dillaman wrote:
What, exactly, is the "reasonably configured hypervisor" here, in other
words, what is it that grabs and releases this lock? It's evidently no
On Tue, Nov 19, 2019 at 4:31 PM Florian Haas wrote:
>
> On 19/11/2019 22:19, Jason Dillaman wrote:
> > On Tue, Nov 19, 2019 at 4:09 PM Florian Haas wrote:
> >>
> >> On 19/11/2019 21:32, Jason Dillaman wrote:
> What, exactly, is the "reasonably configured hypervisor" here, in other
> wor
On 19/11/2019 22:34, Jason Dillaman wrote:
>> Oh totally, I wasn't arguing it was a bad idea for it to do what it
>> does! I just got confused by the fact that our mon logs showed what
>> looked like a (failed) attempt to blacklist an entire client IP address.
>
> There should have been an associa
On Tue, Nov 19, 2019 at 4:42 PM Florian Haas wrote:
>
> On 19/11/2019 22:34, Jason Dillaman wrote:
> >> Oh totally, I wasn't arguing it was a bad idea for it to do what it
> >> does! I just got confused by the fact that our mon logs showed what
> >> looked like a (failed) attempt to blacklist an e
12 matches
Mail list logo
