►
From YouTube: Scalability Team Demo - 2021-10-07
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
C
Well,
all
of
my
instructors
are
still
pending
and
waiting
for
review
and
testing,
so
nothing
new
to
demo.
Today,
maybe
next
week.
A
D
I
mean
I
I
can
show
you
the
apt
wrapper
that
I've
been
working
on.
Maybe
I
I
don't
know
how
interesting
that
is.
A
B
It's
too
bad.
Nobody
involved
with
the
sidekick
redis
thing
the
cpu
spike,
since
the
upgrade
to
sidekick
6
is
on
the
call,
because
I
was
curious
if
somebody
knew
more
about
that
already.
A
Yeah
I
haven't
caught
up
on
any
of
that
this
morning,
yet
yeah
of
all
the
things
we
were
expecting
to
happen,
going
up
was
was
not
one
of
them.
A
D
So
this
is
this
is
the
issue
and
just
to
give
you
a
very
brief
background
on
what
this
even
is.
D
We
see
a
lot
of
chef
failures,
so
this
is
chef
failures
times
three,
because
we
have
three
log
lines
per
failure,
filtering
specifically
on
apt
locks,
so
the
the
type
of
error
that
we
would
get
during
these
failures
is,
you
know,
unable
to
get
lock
or
could
not
get
locked.
There's
a
there's,
a
few
different
locks
inside
of
apt
that
are
affected
by
this,
and
this
has
been
plaguing
us
for
a
long
time.
The
main
two
daily
bursts
that
we
see
correspond
to
two
system:
chrome
jobs
for
unattended
upgrades.
D
One
of
them
does
apt-get
update
the
other
one
does
app
get
update
and
unattended
upgrade,
and
so
that's
kind
of
why
you
see
this
aligned
at,
I
think
it's
6
a.m
and
6
p.m.
Utc,
and
so
the
the
proposed
fix
for
that
which
is
working
in
staging,
looks
like
this.
D
So
this
is
a
bash
script
that
we
add
to
the
path
of
our
chef,
runs
and
also
other
tools
that
that
use
apt-get
or
invoke
apt-get,
and
basically,
it
uses
f
lock
to
obtain
a
a
particular
lock.
That
is
also
used
by
the
unattended
upgrades
script
and
we
name
this
file
apt-get.
D
So
it
gets
invoked
as
if
it
were
apt-get
and
it
will
obtain
the
lock
and
then
shell
out
to
the
actual
apt-get
on
the
inside,
which
is
you
know,
it's
a
little
bit
hacky,
but
it's
got
a
lot
of
nice
properties
doing
it.
This
way,
it's
basically
agnostic
to
whoever
is
calling
it
like.
You
just
add
this,
this
script
to
the
path
and
it
magically
waits
for
the
lock
and
therefore
avoids
those
heart
failures
and
hopefully
reduces
the
amount
of
chef
failures
that
we
see
every
single
day.
D
Apt
errors
out
hard
when
it's
unable
to
obtain
the
lock.
So
I
would
say
this
is
basically
an
apt
bug.
Apt
should
be
waiting
for
that
lock
to
become
available.
D
A
Nice
and
hopefully
those
pages
go
down
that
are
coming
up
because
of
that
failure.