►
From YouTube: 2020-02-14: High availability Gitaly demo
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
A
What
we
have
right
now
is
to
get
early
instances
one
trafficked
instance
and
good
luck,
instant
itself,
it's
configured
and
looked
like
it
works
fine.
The
only
thing
is
that
we
have
only
one
storage
default,
one
because
of
the
configuration
is
that
John
suggested
yesterday
to
me,
because
there
is
yeah
issues
replication,
as
he
said,.
D
A
A
E
A
A
E
A
Yeah
looks
like
so
it's
time
to
check
folks.
A
A
E
A
E
That's
outdated
because
you
have
only
one
piddly
storage,
yeah,
so
one
two
three
four
five,
we
don't
need
six
sounds
more.
No,
that
probably
also
already
happens
add
a
new
file.
You
just
hit
it
with
a
button,
verify
that
are
opposed
to
reduce
correct.
Are
we
at
eleven
or
am
I
going
too
fast?
Now
yeah?
D
E
E
E
A
A
F
F
A
E
E
D
Well,
technically,
it
should
be
read
well
now.
The
second
giggly
is
a
primary.
So
there's
one
config
change.
We
need
to
make
to
the
prefect
combo
directly
and
then
we
can
just
try
bringing
Gidley
to
down
and
then
just
reload
the
page,
so
yeah
not
to
kill
a
bar,
because
the
change
has
not
ended
because
I'm
actually
not
sure
where
the
are.
A
A
A
D
C
A
C
A
D
B
A
D
D
A
A
E
D
C
F
D
C
E
B
B
A
D
A
E
E
A
A
B
A
E
B
A
B
A
B
F
E
A
E
A
E
A
A
A
A
E
E
A
B
E
A
E
E
A
E
E
If
you
would
do
a
failover
back
and
because
now
we
have
data
lost,
because
we
had
a
split
brain
and
we
updated
one
on
the
rights
and
that
change
got
replicated
to
the
left.
So
the
commits
on
the
left
that
we
fail
to
replicate
and
have
now
been
forgotten
because
the
the
refs
have
been
reset
to
whatever
we
did
on
the
rights
right.
Wait
this
fork
and
that
got
applied
on
the
left.
E
B
A
B
B
E
C
A
B
D
E
B
E
B
B
E
B
E
Not
sure
if
it
would,
if
it,
it
would
show
what
happens
with
the
larger
repo,
because
I
think
we're
sort
of
kidding
ourselves
a
little
bit
well
here
replication
is
super
fast
and
then
we
have
production
where
it
takes
two
minutes
and
what
was
what,
where,
where
are
we
on
that
skill?
So
is
it
I?
Don't.
B
D
E
D
E
B
D
One
question
so
the
the
failover
I
like
failover,
that's
in
right.
Now
it's
really
not
like
a
long-term
solution,
because
as
soon
as
you
have
more
than
one
prefect
and
it's
it
can
be
inconsistent.
So
I'm
wondering
didn't
even
want
to
put
that
config
into
on
the
bus,
because
it's
what
we
have
now
sort
of
like
a
very
minimal
feature.
Is
that
yeah,
it's
a
config
value
so.
E
Not
having
an
omnibus
makes
it
harder
to
make
changes,
perhaps
another.
If
you
really
want
it
to
be
a
feature
flag,
you
could
also
use
an
environment
variable
because
you
can
use
a
key
clip
or
be
to
set
environment
variables
in
the
prefect
process,
so
that
would
be
a
way
to
to
cheat
there
and
then
another.
This
thing
where
you
observer
and
reconfigure
and
your
thing
is
gone.
I
guess
the
other
question
is
like
what
what
can
we
is
there
something
we
can
learn
from
having
this?