►
From YouTube: Distribution Demo - Dec 31, 2020
Description
The distribution team demos using a patroni standby cluster for geo replication.
A
Kind
of
very
much
focus
on
booting
up
the
minimal
or
very
close
to
the
minimal
cluster
needed
to
test
to
test
it
in
some
cases,
especially
early
on
the
review
to
be
able
to
iterate
fast
back
and
forth
on
the
review
in
these
test
environments.
So
I'm
actually
using
docker
and
docker
compose
to
set
up
basically
a
full
environment
that
will
exercise
the
standby
cluster,
but
not
not
necessarily
be
an
environment
that
anyone
would
use
in
production.
A
That's
why,
even
though
the
rest
is
redundant
another
the
pg
bouncer
that
I
only
have
one
app
and
then
on
the
geo
side.
It's
basically
a
mirror
of
that
with
three
console
g,
three
consoles
for
geo,
two
geodbs,
a
gopg
bouncer,
a
geo
app
and
I've
also
split
out
the
geo's
tracking
db
into
a
separate
container
as
well.
A
A
A
So
on
the
geo
database
replication,
we
actually
have
a
section
now
on
petroni
support,
and
so
this
is
for
the
database
setup.
My
my
primary
is
basically
following
settings
here.
Main
difference
between
this
and
the
normal
setup
is,
of
course,
rep
manager
is
set
to
false.
We've
got
patrony
set
up
with
pg
rewind,
and
we've
declared
a
physical
replication
slot
for
petroni
to
set
up
in
postgres
and
then
on
the
standby
cluster
side.
A
A
A
A
A
So
one
nice
thing
is
the
the
switch
to
patroni
and
the
use
of
these
standby
clusters
has
made
it
easier
to
set
up
this
sort
of
scenario.
This
was
pretty
difficult,
or
at
least
included
a
lot
of
a
lot
more
configuration
in
order
to
set
up
the
same
sort
of
thing
previously,
with
git
lab
to
set
up
a
secondary
cluster
in
rep
manager.
That
was
replicating
from
the
first
here
in
patroni.
A
A
Basically,
didn't
have
to
write
a
whole
lot
else
under
the
hood.
This
config
right
here
is
being
passed
right
into
patrony
and
that
that
is
settings
up
setting
it
up
for
us.
We
saw
some
limitations
here,
we're
still
working
on
getting
service
discovery
and
console
setup
in
a
way
that
we
can
make
use
of.
A
A
A
C
A
A
A
A
A
A
A
A
A
A
B
A
B
A
A
A
B
B
A
A
B
B
A
A
A
B
A
B
A
A
B
B
B
C
A
A
But
yes,
replication
is
now
set
up
both
on
my
previous
instance
and
on
my
previous
created
project
on
and
on
the
new
one
I
created
with
after
we
had
set
up
the
geo
apps,
okay
that
actually
all
went
better
than
I
was
expecting.
The
main
thing,
that's
still
throwing
errors
is
that
the
geo
log
cursor
is
enabled
on
well
there's
a
couple
things.
The
geo
log
cursor
is
enabled
on
my
database
nodes.
B
A
A
C
A
C
C
A
C
A
B
A
A
A
C
A
Yeah
in
terms
of
reviews,
I'm
working
on
this
because
we
are
we're
trying
to
update
patrony
to
the
2.01
release,
we're
on
1.64
or
something
like
that.
So
I
just
wanted
to
make
sure
that
I
had
environments
that
could
actually
confirm
and
test
that
upgrading
worked
and
needed.
This
standby
cluster
set
up
to
be
able
to
test
the
upgrade.