[pgpool-general: 6197] Re: New master id (%m) is -1 after failover?

Alexander Dorogensky amazinglifetime at gmail.com
Mon Aug 13 09:15:04 JST 2018


Thank you, Tatsuo. I see what caused this error now. Seems like both
databases were down, didn't noticed that.

2018-08-10 12:13:41: pid 1393: WARNING:  All the DB nodes are in down
status and skip writing status file.
2018-08-10 12:13:41: pid 1393: LOG:  failover: no valid backends node found
2018-08-10 12:13:41: pid 1393: LOG:  Restart all children
2018-08-10 12:13:41: pid 1393: LOG:  failover: no follow backends are
degenerated
2018-08-10 12:13:41: pid 1393: LOG:  failover: set new primary node: -1
2018-08-10 12:13:42: pid 1759: DETAIL:  all backend nodes are down, pgpool
requires at least one valid node
2018-08-10 12:13:42: pid 1759: HINT:  repair the backend nodes and restart
pgpool


On Sat, Aug 11, 2018 at 9:20 PM Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> Can you please provide the pgpool.log when failover happens?
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
> > 3.6.9
> >
> > We’re planing to upgrade to 3.6.12
> >
> > On Fri, Aug 10, 2018 at 11:02 PM Tatsuo Ishii <ishii at sraoss.co.jp>
> wrote:
> >
> >> Can you please tell the exact Pgpool-II version?
> >>
> >>
> >>
> >> Best regards,
> >>
> >> --
> >>
> >> Tatsuo Ishii
> >>
> >> SRA OSS, Inc. Japan
> >>
> >> English: http://www.sraoss.co.jp/index_en.php
> >>
> >> Japanese:http://www.sraoss.co.jp
> >>
> >>
> >>
> >> > How is that possible that new master id -1?
> >>
> >> > Is that a valid case?
> >>
> >> >
> >>
> >> > failover_command = '/etc/pgpool-II/failover.sh %d %h %p %D %m %M %H
> %P %r
> >>
> >> > %R'
> >>
> >> > # Executes this command at failover
> >>
> >> > # Special values:
> >>
> >> > #   %d = node id
> >>
> >> > #   %h = host name
> >>
> >> > #   %p = port number
> >>
> >> > #   %D = database cluster path
> >>
> >> > #   %m = new master node id
> >>
> >> > #   %H = hostname of the new master node
> >>
> >> > #   %M = old master node id
> >>
> >> > #   %P = old primary node id
> >>
> >> > #   %r = new master port number
> >>
> >> > #   %R = new master database cluster path
> >>
> >> > #   %% = '%' character
> >>
> >> >
> >>
> >> > failover.sh,
> >>
> >> >
> >>
> >> > failed_node_id=$1
> >>
> >> > failed_host=$2
> >>
> >> > failed_port=$3
> >>
> >> > failed_dir=$4
> >>
> >> > new_master_id=$5
> >>
> >> > old_master_id=$6
> >>
> >> > new_master_host=$7
> >>
> >> > old_primary_node_id=$8
> >>
> >> > new_master_port=$9
> >>
> >> > new_master_dir=${10}
> >>
> >> >
> >>
> >> > failover.log,
> >>
> >> >
> >>
> >> > [ failed node ]
> >>
> >> > failed_node_id         1
> >>
> >> > failed_host            192.168.20.58
> >>
> >> > failed_port            5433
> >>
> >> > failed_dir             /opt/redsky/db/data
> >>
> >> >
> >>
> >> > [ before failover ]
> >>
> >> > old_primary_node_id    1
> >>
> >> > old_master_id          1
> >>
> >> >
> >>
> >> > [ after failover ]
> >>
> >> > new_master_id          -1
> >>
> >> > new_master_host
> >>
> >> > new_master_port
> >>
> >> > new_master_dir
> >>
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20180812/3412f673/attachment.html>


More information about the pgpool-general mailing list