►
From YouTube: 2022-03-07 Database Scalability WG Weekly
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Let's
give
it
another
30
seconds
to
see,
others
would
join
us.
A
Okay,
everyone
welcome
to
the
database.
Scalability
working
group
meeting
today
is
march
7th,
so
I'll
start
from
the
agenda.
The
first
update
is
the
first
item,
a
significant
update
since
last
meeting
from
the
sharding
group.
First
of
all,
huge
thanks
to
jose
and
the
nathan
they
got.
A
The
primary
cluster
reboot
completed
over
the
weekend
very
appreciate
that
effort,
and
now
we
are
unblocked
from
turning
phase
three
on
in
production
and
then
the
follow-up
actions
needs
to
happen
before
we
can
turn
the
phase
straight
on
is
associated
configuration
changes
which
is
described
in
this
in
the
cr.
So
ken
and
ken
was
informed
of
this
cr
and
we
are
looking
for
sres
assistance
to
get
the
cr
implemented
and
take
it
effective
in
the
in
the
environment.
A
Any
questions.
A
The
moving
on
to
the
disaster
recovery
discussion,
the
actually
the
discussion
already
started-
a
very
great
engagement
from
multiple
people
already,
so
that
discussion
is
tracking
as
moving
forward
normal
and
jose
also
created
two
epics
one
is
to
create
a
environment
for
the
testing
and
the
other
is
this
one
just
to
describe
the
the
scenarios
that
failures
could
happen,
then
design
the
test
cases
here.
A
Yeah
fabian
also
suggested
a
risk
matrix
to
to
identify
the
high
priorities
of
the
testing
scenarios.
Mac.
You
want
to
verbalize
your
question.
B
Yeah
thanks:
we
did
some
risk
mapping
exercise
within
the
ops
team
and
I
wonder
if
it
would
be
useful
to
have
an
sd
review
the
plan.
I
think
it's
great
that
everyone's
marching
forward
on
quality
quality
is
everyone's
responsibility,
but
having
another
set
of
eyes
from
the
as
that
would
be,
will
make
the
plan
even
more
solid.
A
Yeah,
I
think
overall,
that's
definitely
going
to
help
and
this
risk
matrix
is
specific
to
the
you
know,
the
failure
mode
of
multiple
databases
and
then
prioritize
those,
but
definitely
as
that
review
will
help
in
my
opinion,
but
camille.
You
have
any
thoughts
here.
C
I
I
don't
have
any
thoughts
at
this
moment.
We
definitely
gonna
have
to
figure
out,
like
the
validation
and
the
testing
plan,
to
to
automate
as
much
of
these
things
and
have,
like
the
let's
say,
move
on
criteria.
D
Yeah
we
can
pull
in
an
sct
here
to
help.
I
think
one
thing
to
highlight
is
that
in
the
past,
wrist
maps
and
risk
matrices
have
taken
quite
a
few
weeks.
It's
not
a
quick
process.
It
takes
a
while
to
make
sure
that
you
fully
understand
things
and
can
can
identify
them
and
have
them
written
up.
So
there
would
be
some
trade-offs
since
we
don't
have
an
sct
in
this
area.
So
we
need
to
figure
out
what
trade-offs
need
to
happen
to
to
accommodate
that.
But
we
can
absolutely
find
somebody
to
take
that
on.
A
Thank
you
and
we
still
have
some
time
here.
This
task
is
really
targeting
for
a
phase
seven,
so
yeah
phase,
seven
is
the
last
one.
So
we
we
still
have
some
time
here.
A
Our
phase
seven
wrap-up
target
line
is
wrapping
up
on
the
may
20th
at
this
moment.
So
there
is
update
later
here
in
the
review,
a
roll
out
process.
So
you
can
see
the
timeline
here,
I'm
highlighting
that
epic,
so
yeah,
that's.
The
timeline
looks
like
right
now.
E
Is
actually
different
from
the
disaster
recovery
working
group?
This
is
thinking
about
the
specific
disaster
scenarios
for
rolling
out
the
decomposed
database,
so
this
is
separate
from
the
the
geo
for
disaster
recovery.
That's.
A
Right,
okay,
correct
yeah:
this
is
another
general
disaster
recovery.
This
is
about
the
failure
mode
and
we
test
those
failures
and
see
how
we
can
recover
from
anything
that
unexpected
from
this
decomposed
databases.
B
All
right,
thank
you,
tanya
would
know
no
best,
though.
A
You
thank
you
next
item
minor
one.
We
still,
we
are
still
looking
for
some
additional
ivs
of
front-end
engineers
to
test
drive
the
multiple
databases
gdk.
I
will
continue
to
reach
out
and
see
a
any
volunteers
available
and
we
already
identified.
We
already
got
many
volunteers
from
different
functional
groups
like
a
vt
tech,
writing
and
ux.
So
we
have
a
good
coverage
there.
A
Okay,
sam
and
tim
are
not
here
steve
here,
nope
so
looks
like
I
need
to
just
to
follow
up
with
steve
or
ken
to
on
the
on
the
change
request
I
mentioned
earlier
and
then
moving
on
to
next
review
the
rollout
progress
so
our
based
on
current
progress.
Our
project
timeline
was
updated
last
week
and
now
projecting
may
20th
to
fully
deploy
the
phase
seven
in
production.
A
Okay,
then,
moving
on
to
review
the
progress
charts
here.
Overall,
our
outstanding
development
issues
keep
trending
down
and
our
mr
pace
is
on
track.
The
charts
are
captured
here,
the
screenshots
is
below
here.
So
it
looks
as
looking
at
the
right
trend
here
and
risks
and
number
four
and
five
nothing
to
update
here
and
number
six
others
jerry.
You
want
to
verbalize
your
comment.
F
I'm
just
yelling
about
this
anywhere
I
go
to
so
you
can
go
review
that,
mr,
because
we're
seeing
more
requests
for
beta
stores
and
so
trying
to
write
some
guidance
to
developers
and
anyone
else
as
to
how
we
think
about
this
and
trying
to
help
people
get
to
the
right
places,
because
right
now,
they're
coming,
you
know
either
I
hear
about
something
or
something
tells
me
something.
So
we
are
trying
to
offer
a
little
bit
of
guidance
on
how
people
can
should
go
about
storing.
A
Data.
Thank
you
is
this.
The
the
news
thing
I
mean
spin
spawn
from
the
the
discussion
of
another
data
store
in
from
the
what
was
that
feature.
F
There
were
two
requests
recently:
one
of
them
was
reviewer
recommender
and
then
the
other
one
is
the
work.
That's
been
done
for
upstraights,
which
likely
looks
like
it's
going
to
introduce
a
brand
new
data
store.
So
in
in
various
conversations
I
I
keep
running
into
people
that
are
thinking
about
new
databases
and
so
just
trying
to
put
some
structure
around
that
right.
A
Thank
you
so
so
somebody
like
it
helps
by
bringing
this
to
the
development
community
or
our
development
channel
to
make
sure
that
everyone
is
aware
of
those
guidelines
as
being
articulated
cool.
Thank
you.
A
And
mack.
B
Yes,
thank
you
so
we're
using
the
data
from
this
group
the
functional
decomposition
to
build
out
the
dashboards
at
the
stakeholder
level.
So
I
think,
when
we're
in
a
stable
state
of
engineering,
velocity
and
less
on
engineer
locations
with
normal
maintenance
going
forward
and
we're
picking
the
data
here
to
to
try
out
those
dashboards,
I'm
trying
to
render
the
backlog
within
the
infrastructure
team
within
the
different
teams.