On Mon, 2019-07-08 at 13:11 +0900, 김동현 wrote:
> Hello.
> I'm Donghyun Kim.
>
> I work as a system engineer in Korea.
>
> In the meantime, I was very interested in the cluster and want to
> promote it in Korea.
> There are many high-availability cases in Linux systems.
>
> The reason why I am
On Tue, Jul 9, 2019 at 4:21 PM Jehan-Guillaume de Rorthais
wrote:
> On Tue, 9 Jul 2019 13:22:06 +0200
> Tiemen Ruiten wrote:
>
> > On Mon, Jul 8, 2019 at 10:01 PM Jehan-Guillaume de Rorthais <
> j...@dalibo.com>
> ...
> > > I dig in xlog.c today. Maybe I can write a small extension to get the
>
On Tue, 2019-07-09 at 12:54 +, Michael Powell wrote:
> I have a two-node cluster with a problem. If I start
Not so much a problem as a configuration choice :)
There are trade-offs in any case.
- wait_for_all in corosync.conf: If set, this will make each starting
node wait until it sees
On Tue, 2019-07-09 at 11:21 +0100, lejeczek wrote:
> hi guys,
>
> how to, if possible, create colocation which would not stop dependent
> resources if the target(that would be systemd agent) resource fails
> on
> all nodes?
>
> many thanks, L.
Sure, just use a finite score. Colocation is
09.07.2019 13:08, Danka Ivanović пишет:
> Hi I didn't manage to start master with postgres, even if I increased start
> timeout. I checked executable paths and start options.
> When cluster is running with manually started master and slave started over
> pacemaker, everything works ok. Today we
On Tue, 9 Jul 2019 13:22:06 +0200
Tiemen Ruiten wrote:
> On Mon, Jul 8, 2019 at 10:01 PM Jehan-Guillaume de Rorthais
...
> > I dig in xlog.c today. Maybe I can write a small extension to get the
> > timeline
> > from shared memory directly and make pgsqlms use it if it detects it. So
> > people
On Tue, Jul 9, 2019 at 3:54 PM Michael Powell <
michael.pow...@harmonicinc.com> wrote:
> I have a two-node cluster with a problem. If I start Corosync/Pacemaker
> on one node, and then delay startup on the 2nd node (which is otherwise
> up and running), the 2nd node will be rebooted very soon
I have a two-node cluster with a problem. If I start Corosync/Pacemaker on one
node, and then delay startup on the 2nd node (which is otherwise up and
running), the 2nd node will be rebooted very soon after STONITH is enabled on
the first node. This reboot seems to be gratuitous and could
Hello Kim,
On 08/07/19 13:11 +0900, 김동현 wrote:
> I'm Donghyun Kim.
>
> I work as a system engineer in Korea.
>
> In the meantime, I was very interested in the cluster and want
> to promote it in Korea.
> There are many high-availability cases in Linux systems.
>
> The reason why I am sending
On Mon, Jul 8, 2019 at 10:01 PM Jehan-Guillaume de Rorthais
wrote:
> I should have step up to this thread, sorry :)
>
Really appreciate all the assistance so far.
> The real problem is not how much xact you will lost during failover, but
> how we
> can choose the best standby to elect. This
hi guys,
how to, if possible, create colocation which would not stop dependent
resources if the target(that would be systemd agent) resource fails on
all nodes?
many thanks, L.
pEpkey.asc
Description: application/pgp-keys
___
Manage your
11 matches
Mail list logo
