All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
To: Samuel Just <sjust@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Rados multi-object transaction use cases
Date: Fri, 12 Jun 2015 18:21:07 -0400 (EDT)	[thread overview]
Message-ID: <1019086990.13871273.1434147667441.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1235935092.20915764.1434147302334.JavaMail.zimbra@redhat.com>



----- Original Message -----
> From: "Samuel Just" <sjust@redhat.com>
> To: "ceph-devel" <ceph-devel@vger.kernel.org>
> Sent: Friday, June 12, 2015 3:15:02 PM
> Subject: Rados multi-object transaction use cases
> 
> In the Infernalis CDS, we had a session on RADOS multi-object transactions.
> I'd like to continue the discussion at the upcoming Jewel CDS.  I thought
> I'd prime the discussion by asking: if librados supported multi-object read
> and write transactions, what would you use them for?  Some idea of use cases
> would be valuable when considering things like deadlock coping strategies.

Here are a few for rgw:
 - update bucket index when creating / modifying / deleting an object
 - store multiple metadata objects atomically: e.g., user info + user access keys + user email (currently not atomic)
 - store bucket entry point + bucket instance info atomically
 - creating a bucket and adding it to the user's list of buckets

Yehuda

  reply	other threads:[~2015-06-12 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1237345102.20915406.1434147190410.JavaMail.zimbra@redhat.com>
2015-06-12 22:15 ` Rados multi-object transaction use cases Samuel Just
2015-06-12 22:21   ` Yehuda Sadeh-Weinraub [this message]
2015-06-12 22:28     ` Somnath Roy
2015-06-13  2:42   ` Li Wang

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=1019086990.13871273.1434147667441.JavaMail.zimbra@redhat.com \
    --to=yehuda@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sjust@redhat.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.