►
From YouTube: 2022-03-14 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
Okay,
let's
get
started,
we
are
at
the
time
so
welcome.
Everyone
today
is
march
14th.
This
is
the
database
scalability
working
group
weekly
meeting.
Let's
get
started
from
the
agenda.
First
significant
updates.
Since
the
last
meeting
I
have
the
first
I
done.
I
did
an
item
updates
from
the
starting
group
and
overall.
So
thanks
for
to
j
to
jose
and
the
nathan's
preservers,
the
ci,
the
production
cia
cluster
was
ready
earlier
today.
A
So
now
we
are
we're
good
proceeding
to
turn
the
fish
phase
three
feature
flag
on
to
split
the
ci
raid
traffic
in
the
in
the
production
environment.
So
excited
about
that.
This
is
going
to
happen
really
short,
very
so,
hopefully,
today
or
early
tomorrow,
and
also
development
has
completed
all
the
face
for
issues
yeah
close
to
all
the
development
teams,
and
then
we
are
now
focusing
on
the
phase
six
outstanding
issues,
and
we
are
done
tonight
at
this
moment
from
last
week.
Last
week
it
was
30.
A
A
So,
of
course,
as
we
move
forward,
if
we
discover
new
issues,
we
will
just
reopen
those
epics
and
then
work
on
the
new
discovery
issues,
and
also
here
is
a
discussion
about
the
downtime
that
we
we
will
be
testing
in
phase
five
and
that
downtime
will
be
necessary
for
phase
seven.
We
will
do
multiple
dry
runs
and
the
test
against
the
stone
time.
A
But
overall
the
feeling
is
that
the
downtime
is
ideally
less
than
a
couple
of
minutes
and
technically
some
parts
of
the
gitlab
will
work
the
hallways
through
the
migrations
and
that's
basically
anything
that
isn't
ci.
So
it's
not
a
full
down
time.
It's
basically
just
the
sum
rise
to
the
ci
tables
will
be
blocked
that
occurred
during
that
window.
So,
in
phase
seven,
when
we
roll
the
decomposition
completely
to
production,
the
ci
rate
will
be
blocked
for
a
short
time
of
the
window.
A
Yeah,
it's
basically
syncing
the
data
from
the
main
database
to
the
ci
cluster,
so
we
want
to
stop
writing
to
the
main
cluster.
Then
sync,
data
to
the
ci
cluster
then
switch
the
ci
both
read
and
write
to
the
ci
cluster,
so
that
downtime
is
basically
for
data
syncing.
A
Okay
last
item,
I
asked
the
update
for
me.
There
aren't
there
aren't
any
force,
forcing
major
tasks
for
infrastructure
in
phase
five
and
six.
Basically,
those
two
phases
we're
going
to
do
a
lot
of
testing
and
the
validation
of
the
raw
procedure
and,
of
course,
there
will
be
there
might
be
small
discoveries,
so
that
could
be
something
that
the
infrastructure
will
need
to
resolve
error
out.
A
Meanwhile,
we
can
focus
during
that
time
frame.
We
can
focus
on
preparing
for
service.
For
example,
there
are
other
procedure
and
disaster
disaster
recovery
mechanisms.
So
that's
what
infrastructure
and
the
development
can
do
during
that
validation
phase.
A
Okay,
then
move
on
to
the
roll
out
progress
review.
I
have
a
few
points
here.
First,
there's
no
change,
no
change
to
timeline
and
the
confidence
level.
This
week
we
are
proceeding
to
phase
three
in
production.
At
this
point
and
also
while
rolling
the
phase
three
out
in
production,
development
and
sre
can
collaborate
on
preparing
phase
four
staging
role
out.
A
A
And
also
thank
you
thanks
to
jose
for
preparing
a
template
for
the
decomposition,
rollout
and
future
maintenance.
This
template
once
we
have
it
ready,
it
will
greatly
mature
the
process
and
provide
transparency
for
any
major
maintenance
or
upgrades
of
the
decomposed
databases.
A
At
this
point,
no
everything
we
are
working
on.
Every
team
is
working
on
physics,
so
yeah
we
are
we're
good.
All
the
development
teams
are
looking
good.
C
I
think
the
only
outstanding
issue
in
ops
is
something
that
on
us
is
actively
working
on,
which
is
the
cio
and
runner
cross
joining
bits
that
are
pretty
tricky,
but
we
only
need
them
a
bit
later
and
that's
the
last
outstanding
issue.
As
far
as
I'm
aware
of.
B
A
Yeah
for
ups,
there
is
a
one
for
phase
six,
it's
being
worked
out.
We
are
pretty
close
another
one
for
face
seven
and
the
starting
group
picked
up.
So
we
we
are
working
on
that.
A
Okay,
then
bullish
three
review,
the
progress
charts.
I
posted
the
chart
here
so
on
development
side.
We
are
looking
good
or
continuous
trend,
outstanding
issues,
continuous
up,
yeah.
C
I
personally,
like
I
don't
know-
maybe
maybe
it's
just
a
number,
but
I
still
find
it
pretty
astounding
that
we
have
more
than
500
merged,
mrs
just
in
that
one
epic
and
that's
across
you
know:
dev
ops,
secure
the
enablement
sections
and
the
sharding
team
itself.
So
I
think
that's
pretty
pretty
exciting.