On Sat, Sep 23, 2023 at 5:05 AM Matthias Ferdinand wrote:
>
> On Fri, Sep 22, 2023 at 06:09:57PM -0400, Casey Bodley wrote:
> > each radosgw does maintain its own cache for certain metadata like
> > users and buckets. when one radosgw writes to a metadata object, it
> > broadcasts a notification (
On Fri, Sep 22, 2023 at 06:09:57PM -0400, Casey Bodley wrote:
> each radosgw does maintain its own cache for certain metadata like
> users and buckets. when one radosgw writes to a metadata object, it
> broadcasts a notification (using rados watch/notify) to other radosgws
> to update/invalidate th
each radosgw does maintain its own cache for certain metadata like
users and buckets. when one radosgw writes to a metadata object, it
broadcasts a notification (using rados watch/notify) to other radosgws
to update/invalidate their caches. the initiating radosgw waits for
all watch/notify response
On Tue, Sep 12, 2023 at 07:13:13PM +0200, Matthias Ferdinand wrote:
> On Mon, Sep 11, 2023 at 02:37:59PM -0400, Matt Benjamin wrote:
> > Yes, it's also strongly consistent. It's also last writer wins, though, so
> > two clients somehow permitted to contend for updating policy could
> > overwrite e
On Mon, Sep 11, 2023 at 02:37:59PM -0400, Matt Benjamin wrote:
> Yes, it's also strongly consistent. It's also last writer wins, though, so
> two clients somehow permitted to contend for updating policy could
> overwrite each other's changes, just as with objects.
Hi, thank you for confirming thi
Yes, it's also strongly consistent. It's also last writer wins, though, so
two clients somehow permitted to contend for updating policy could
overwrite each other's changes, just as with objects.
Matt
On Mon, Sep 11, 2023 at 2:21 PM Matthias Ferdinand
wrote:
> Hi,
>
> while I don't currently u
