►
From YouTube: CDS Hammer (Day 1) - RGW: Bucket Index Scalability
Description
http://goo.gl/U4b70r
28 October 2014
Ceph Developer Summit: Hammer
Day 1
RGW: Bucket Index Scalability
Guang Yang
A
So
the
upside
for
the
next
one,
the
bucket
scalability
or
bucket
index
scalability
I
guess-
is
that
it's
a
holdover
from
the
gh
summit,
so
there's
actually
a
pretty
detailed
pad.
If
you
look
at
the
blueprint,
as
well
as
a
decent,
detailed
description,
well,
maybe
we
could
just
hammer
through
some
of
his
points
and
look
at
the
status
and
then
we
can
take
it
to
the
list
after
after
the
summit.
When
he's
able
to
talk
about
it,.
C
B
B
Yeah
we've
been
through
various
cycle
for
free
few,
most
of
it
is
done,
and
most
of
it
is
ready.
The
thing
the
main
thing
that
it
already
is
yeah,
but
tying
it
up
with
the
multi
region,
multi-zone
stuff,
because
the
the
problem
is,
we
have
some
logs
with
it
resides
within
the
packet
injection.
We
need
to
make
sure
that
everything
works
correctly
and
there
are
maybe
just
choosing
different
kind
of
markers
to
tune
for
the
food,
the
multi
region
for
further,
when
we
have
shouted
bucket
index.
B
B
So
yeah,
so
so
the
the
feature
is
is
going
along
pretty
nicely.
We
try
to
grind.
What's
working
on
it,
we
were
trying
to
make
it
everything
obstructed
nicely
so
that
we
don't
try
the
same
thing
over
and
over
and
over,
because
we
it
was
changing
the
current
all
packet
access
Taffy's
in
synchronous,
asynchronous
greatest
operations,
most
of
it
and
now
everything
needed
to
change,
because
when
you
do
operations
on
concurrently
in
multiple
back
it
charged.
B
C
So
it
looks
like
an
ideal
etherpad
and
we
talked
about
adding
two
different
list
commands,
so
you
can
do
the
regular
traditional
list.
That'll
still
return,
the
same,
ordered
results
and
would
sort
of
read
from
all
shards
in
parallel
and
aggregate
the
results
of
the
client
side
and
then
also
adding
a
new
list.
Unordered
command.
That
would
sort
of.
B
C
Yeah
I
won't
matter
yeah,
yes,
okay,
I,
remember
there
was
one
question
that
I
think
I
think
maybe
you
were
on
vacation
when
they
did
this
last
time
there
was
one
question
about
the
atomicity
of
the
multi-part
upload.
A
C
B
B
C
B
Well,
in
terms
of
the
object,
avenging
branches,
I
had
I
kind
of
did
some
a
few
major
cleanups,
so
my
changes
go
out
or
no
other.
B
Over
the
place,
and
so
they're
gonna
be
lots
of
conflicts,
but
I
don't
think
that
anything
specific
yeah
yeah
big,
because
the
we
didn't
really
touch
the
same
areas
other
than
in
tactic
changes
here
and
there
and
I'm
not
not
afraid
to
merge.
I
well,
I
think
before
have
tried
to
get
better
I
I,
don't
think.
There's
gonna
be
a
major
issue
issue:
okay,.
B
B
Him
you're
gonna,
okay,
all.
C
B
That'd
be
nice,
it
would
be
nasty
of
someone
helping
there
in
that
area.
There's
some
pending
code
that
I
still
need
to
review,
though
oh
and
we
need
to
have
some
discussion
about
what
the
next
steps
gonna
be.
But
in
testing
sonam
require
some
time
testing
and
and
then
we
we
need
to
think
whether
that's
only
phase
one
and
phase
one
is
basically
you
take
her
back
it
and
say
this
bucket
is
gonna,
be
no
has
at
least
many
shots.
B
B
There
there
can
be
different
approaches.
One
would
be
like
quiesce
all
the
rights
to
to
that
bucket
and
convert
it
to
20
shouted
one
which
should
be
I.
Guess
should
work
somehow,
like
probably
not
the
most
elegant
solution,
but
much
should
be
pretty
easy
to
wear
up,
except
for
creating
rights
which
is
not
something
that
we
we
really
do
be
good
but
yeah.
Let's
say.
C
C
C
C
A
B
But
nah
nowadays
we
cash
it.
We
have
a
double
double
layer,
cash,
double
gate.
We
actually
cash,
the
packet
info,
her
and
accredit
yeah
and
decoded
busting
bucket
info
well
to
save
the
encoding
decoding
that
happens
used
to
happen
every
own
operation.
C
B
So
yeah,
so
that
would
basically
do
it.
So
I
don't
know
if
there
is
any
need
to
do
something
more
come
more
complicated
than.