►
From YouTube: 2020 09 08 Database Team Meeting
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
All
right
see
it's
tuesday
september
8th.
I
have
the
wrong
date
on
here.
Database
team
meetings
jump
right
into
it.
I
looked
at
the
urgent
issues,
looks
like
andreas
answered,
both
of
them.
Thank
you
doesn't
look
like
there's
really
anything
for
us
to
do
at
the
moment.
Let's
get
some
feedback
on
the
first
one
and
we
are
awaiting
feedback
from
robert
marshall
on
the
second
one.
B
For
the
first
one,
there
is
a
few
follow-ups
I
want
to
do,
but
the
main
part
is
basically.
I
think
I
don't
think
it's
a
code
change
that
we
wanted.
We
want
to
do
so.
I
think
this
is
rather
an
omnibus
thing,
and
I'm
probably
checking
in
today
with
the
distribution
team
and
see
if
they
can
take
it
or
how
we
would
do
it
on
good
platform.
I
don't
think
that
should
go
into
the
application,
because
it's
just
a
configuration
change.
A
A
All
right,
I
thought
I'd
link
this
here,
so
I'm
taking
part
of
the
manager
challenge
pilot
program
and
I
linked
the
overall
program
there.
It's
a
four
week
program,
they've
asked
for
a
few
volunteers
from
the
management
group
to
participate
in
this
and
once
they've
gone
through
the
pilot,
they
will
actually
roll
out
to
a
larger
group.
A
Part
of
the
day.
One
activity
was
take
a
self-assessment
on
social
style
and
then
linked
it
there.
If
you
all
want
to
take
it,
we
can
share
later
and
I'll.
Let
you
all
take
it
first,
if
you're
interested
and
then
I
will
share
my
results
later,
you
can
guess,
as
as
to
where
I
land
it's
pretty
interesting.
Actually
so
take
a
look.
Let
me
know
how
and
if
you
want
to
participate,
and
if
you
don't
it's
perfectly
fine.
B
I
was
looking
at
the
assessment.
I
was
wondering
if
there
is
sort
of
an
explanation
what
those
individual
things
are
like.
You
know
when
they,
when
you
you're
supposed
to
write
yourself
on
for
like
into
in
one
dimension,
is
there
more
explanation
with
regard
to
what
this
means.
A
A
A
It
looks
like
someone
actually
created
a
social
styles
application
to
make
the
testing
a
little
more
interesting.
All
right,
I
haven't
seen
this
either
cool.
I
will
link
this
in.
A
A
All
right
some
goals
from
last
week
we
already
reviewed
onto
events,
epic,
we're
blocked
right.
Now,
it's
still
on
the
ux.
I
need
to
follow
up
on
that
and
we're
going
to
try
and
get
it
done
13-4,
but
we're
running
out
of
time.
So
it
looks
like
us
finishing
up.
Audit
events
will
carry
over
to
13.5
container
registry.
You
all
had
a
meeting
to
discuss.
I
wasn't
a
part
of
that.
Was
there
any
outcome
on
that?
One.
B
We
have
a
follow-up.
This
week,
shaw
was
back
and
he's
looking
at
the
all
the
things
that
we
discussed
and
we
have
a
meeting
on
thursday
to
run
through
those.
B
Oh
yeah,
okay,
wednesday,
but
so
far
what
we've
seen
is.
We
think
it
is
a
viable
alternative,
but
it's
going
to
be
interesting
to
see
what
he
thinks
about
it.
A
Yeah:
okay,
giannis,
how
you
doing
on
the
database
instrumentation.
C
I
will
send
the
dmr
today,
I'm
having
fun
with
maca
laptops.
I
miss
my
linux
laptop.
I
really
miss
my
linux
laptop.
I
cannot
make
a
gitlab
compose
kit
work
with
mac.
I
just
can't
I
get
bad
gateways,
it's
it
cannot
work
so
yeah.
I
I'm
running
a
different
configuration
now,
so
I'm
running
prometheus
in
a
docker
and
then
I'm
running
jdk
and
then
I'm
connecting
jdk
to
prometheus
to
jdk
and
scraping
my
jdk.
So
I
think
that
works
so.
A
C
C
Do
that
so,
but
I
I
do
so,
I
have
lost
a
day,
but
I
don't
want
to
generate
an
image.
So
the
easy
way
around
is
to
just
generate
an
image
from
only
bus.
B
C
C
A
B
I
did
not
no
the
other
things
to
priority
like
container
registry
and
yeah.
Look
balancing
stuff.
A
A
few
things
popped
up
this
week
was
there
any
progress,
anybody
know
on
the
rake
task
or
maybe
pg
repack.
Jose
is
not
here.
B
Yeah,
the
so
pat's
working
on
that,
so
I
think
he's
got
the
mr
ready
for
the
like
the
first
iteration
on
that
providing
a
rake
task
for
the
re-indexing.
That's
that's
short
before
review.
I
think,
and
it's
looking
good
and
then
I
I
took
a
look
at
the
good
luck,
calm
state
and
we
currently
have
three
packing
schedules.
B
So
that's
about
to
be
picked
up
again
from
the
sme
teams,
but
looking
at
the
blood
statistics,
I
don't
know
if
you
all
saw
that
it's
getting
more
and
more
so
we
have
like
more
than
two
terabytes
of
floats
from
for
the
total
database
size
of
like
eight
terabytes
or
so
so
it's
like
a
lot
and
yeah.
I
would
love
to
get
that
going
on
the
applications
like
because
I
think
this
is
something
that
we
have
to
do
more
regularly
and
it's
just
like
looking
at
how
sre
teams
currently
do
that.
B
I
think
this
is
a
lot
of
effort
for
them
to
get
it
scheduled
to
get
it
reviewed
to
execute
on
it
and
then
eventually,
the
next
month.
You
have
to
do
it
over
again,
so
yeah
I'd
love
to
get
that
next
into
the
next
milestone
as
well,
that
we
continue
on
that
and
there's
two
follow-ups
to
what
pat
is
working
on
like
once.
We
have
the
rake
task
in
place.
B
The
next
milestone
is
basically
preventing
this
re-indexing
to
interfere
with
deployments,
because
this
is
what
can
happen
when
you
do
the
re-indexing
in
background,
so
that
you're,
taking
up
a
lock
on
that
and
then
deployment
runs,
runs
database,
migrations
and
then
you're,
basically
blocking
the
deployment
from
a
background
job,
and
I
think
we
can
detect
this
and
sort
of
cancel
the
background
job,
because
it's
not
as
important
as
a
deployment.
A
B
Right
away,
okay,
it
was
blocked
for
for
a
different
reason,
but
now
they're
picking
it
up
again.
Yeah.
A
I
was
gonna
say
we
run
through
the
board
real,
quick,
there's,
a
handful
of
unassigned
issues.
Are
there
any
high
level
goals?
We
want
to
talk
about.
A
A
I'm
putting
words
into
your
mouth
here,
you
honestly
did
you
want
to
try
and
finish
this
this
week.
C
Yeah
we
do
we'll
send
the
mr
for,
for
the
first,
mr
we'll
add
it
to
omnibus
and
when
it's
merged
I
will
test
with
the
image
and
send
the
dmr
for
all
the
beings.
So
it's
you
need
first,
the
omnibus
so,
but
I
have
ready
the
other
one.
It's
just
having
a
after
the
ones
done.
I
present
for
you
the
other
one.
A
A
C
I'm
thinking
of
working
through.
C
A
A
A
A
So
I
was
reviewing
this
one
this
morning.
Do
we
still
want
to
do
this
or
these
types
of
design
decisions
already
covered
in
existing
documentation,
and
I
haven't
reviewed
our
documentation
that
we
already
have
out
there
in
the
handbook
andreas?
I
know
you
wrote
some
great
write-ups
on
different
partitioning
considerations,
but
is
that
material
pretty
well
covered
for
what
we
would
talk
about
here?
Maybe
if
it
is,
we
just
add
an
addendum
to
it
just
saying
this
is
why
we
did
auditing
events.
Audit
events
partitioning
this
way
or
see.
B
A
A
B
A
B
We
could
really
start
very
basic
with
that,
so
I
realized
that
the
the
database
load
balancing
the
application
side
load
balancing
that
is
that
always
excludes
sidekick
from
it
right,
so
any
sidekick
or
rake
task.
They
don't
make
use
of
the
load
balancing.
So
that
means
we
never
spread
out
the
the
read
queries
to
replicas
for
psychic
jobs.
B
And
we
could
start
very
simple
and
sort
of
tag.
All
the
jobs
read
write,
so
that
would
still
all
go
to
the
to
the
primary
and
then
start
with
one
job
and
mark
it
as
as
read
only
and
see
if
that
goes.
A
B
Let
that
go
to
the
replica
that
would
make
for
a
good
first
step.
I
think.
A
A
A
Okay,
we
talked
about
that
one,
that's
pat's!
Oh
this
one's
still
realistic
for
this
milestone.
C
Leave
it
there,
I
want
to
check
it
out
one
more
time.
A
C
B
This
is
ready
for
reviews,
which
is
a
small
change,
the
same
as
the
last
one.
This
is
also
just
a
three
line:
change.
B
For
this
one,
it's
the
question
like:
do:
we
want
to
spend
more
time
on
it
if
that
is
in
sort
of
an
acceptable
direction?
How
do
we
work
with
the
container
history
team?
Do
they
pick
it
up
from
there,
but
I
would
wait
for
for
the
wednesday
meeting
to
to
discuss
stuff
further
yep.