GPDB的spread方式测试

最新推荐文章于 2024-08-21 12:04:21 发布
原创 最新推荐文章于 2024-08-21 12:04:21 发布 · 1.2k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#gpdb

本文介绍GPDB中mirror的两种配置方式，默认group方式可能导致性能瓶颈，推荐使用spread模式提高可用性和性能。通过实操演示了在一台主机宕机后，如何通过gprecoverseg命令恢复系统并确保数据一致性。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

在GPDB的mirror安装中，有两种方法，默认的group方式是将A机器备份在B机器上，这种方式有一个弊端，在A机器宕机后，B机器上就运行了*2的节点数量的运算和存储，这样势必导致整个集群的运算性能极具下降，甚至不能使用；因此官方也推荐mirror的使用方式为spread，前提是机器的segment host数量为每台机器上的segment+1，举个例子：有4台机器作为seghost，每单机器3个segment,分别abcd机器，abcd每台机器上有seg1 seg2 seg3,对应关系如下

机器名   节点名        mirror机器名    mirror节点名
A        seg1        B               seg2
A        seg2        C               seg3
A        seg3        D               seg1
....

以上只是实例，当时实际情况不可能这么规整，具体的对应关系可以使用gpstate -c查看，例如我实际的对应关系如下

20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-Obtaining Segment details from master...
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:--Current GPDB mirror list and status
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:--Type = Spread
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Status                             Data State     Primary      Datadir                               Port    Mirror       Datadir                               Port
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue02-em1   /home/gpadmin/data/gpdatap1/gpseg0    40000   blue03-em2   /home/gpadmin/data/gpdatam1/gpseg0    50000
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue02-em2   /home/gpadmin/data/gpdatap2/gpseg1    40001   blue04-em3   /home/gpadmin/data/gpdatam2/gpseg1    50001
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue02-em3   /home/gpadmin/data/gpdatap3/gpseg2    40002   blue05-em1   /home/gpadmin/data/gpdatam3/gpseg2    50002
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue03-em1   /home/gpadmin/data/gpdatap1/gpseg3    40000   blue04-em2   /home/gpadmin/data/gpdatam1/gpseg3    50000
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue03-em2   /home/gpadmin/data/gpdatap2/gpseg4    40001   blue05-em3   /home/gpadmin/data/gpdatam2/gpseg4    50001
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue03-em3   /home/gpadmin/data/gpdatap3/gpseg5    40002   blue02-em1   /home/gpadmin/data/gpdatam3/gpseg5    50002
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue04-em1   /home/gpadmin/data/gpdatap1/gpseg6    40000   blue05-em2   /home/gpadmin/data/gpdatam1/gpseg6    50000
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue04-em2   /home/gpadmin/data/gpdatap2/gpseg7    40001   blue02-em3   /home/gpadmin/data/gpdatam2/gpseg7    50001
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue04-em3   /home/gpadmin/data/gpdatap3/gpseg8    40002   blue03-em1   /home/gpadmin/data/gpdatam3/gpseg8    50002
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue05-em1   /home/gpadmin/data/gpdatap1/gpseg9    40000   blue02-em2   /home/gpadmin/data/gpdatam1/gpseg9    50000
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue05-em2   /home/gpadmin/data/gpdatap2/gpseg10   40001   blue03-em3   /home/gpadmin/data/gpdatam2/gpseg10   50001
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:-   Primary Active, Mirror Available   Synchronized   blue05-em3   /home/gpadmin/data/gpdatap3/gpseg11   40002   blue04-em1   /home/gpadmin/data/gpdatam3/gpseg11   50002
20160816:13:59:43:018642 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------

以下我们验证采用spread方式后，在一台机器宕机后，查看mirror的启动及数据分配情况。
1.down机前检查机器情况重点内容

select * from gp_segment_configuration order by 1;

 dbid | content | role | preferred_role | mode | status | port  |  hostname  |  address   | replication_port | san_mounts 
------+---------+------+----------------+------+--------+-------+------------+------------+------------------+------------
    1 |      -1 | p    | p              | s    | u      |  5432 | blue01-em1 | blue01-em1 |                  | 
    2 |       0 | p    | p              | s    | u      | 40000 | blue02-em1 | blue02-em1 |            41000 | 
    3 |       1 | p    | p              | s    | u      | 40001 | blue02-em1 | blue02-em2 |            41001 | 
    4 |       2 | p    | p              | s    | u      | 40002 | blue02-em1 | blue02-em3 |            41002 | 
    5 |       3 | p    | p              | s    | u      | 40000 | blue03-em1 | blue03-em1 |            41000 | 
    6 |       4 | p    | p              | s    | u      | 40001 | blue03-em1 | blue03-em2 |            41001 | 
    7 |       5 | p    | p              | s    | u      | 40002 | blue03-em1 | blue03-em3 |            41002 | 
    8 |       6 | p    | p              | s    | u      | 40000 | blue04-em1 | blue04-em1 |            41000 | 
    9 |       7 | p    | p              | s    | u      | 40001 | blue04-em1 | blue04-em2 |            41001 | 
   10 |       8 | p    | p              | s    | u      | 40002 | blue04-em1 | blue04-em3 |            41002 | 
   11 |       9 | p    | p              | s    | u      | 40000 | blue05-em1 | blue05-em1 |            41000 | 
   12 |      10 | p    | p              | s    | u      | 40001 | blue05-em1 | blue05-em2 |            41001 | 
   13 |      11 | p    | p              | s    | u      | 40002 | blue05-em1 | blue05-em3 |            41002 | 
   14 |       0 | m    | m              | s    | u      | 50000 | blue03-em1 | blue03-em2 |            51000 | 
   15 |       1 | m    | m              | s    | u      | 50001 | blue04-em1 | blue04-em3 |            51001 | 
   16 |       2 | m    | m              | s    | u      | 50002 | blue05-em1 | blue05-em1 |            51002 | 
   17 |       3 | m    | m              | s    | u      | 50000 | blue04-em1 | blue04-em2 |            51000 | 
   18 |       4 | m    | m              | s    | u      | 50001 | blue05-em1 | blue05-em3 |            51001 | 
   19 |       5 | m    | m              | s    | u      | 50002 | blue02-em1 | blue02-em1 |            51002 | 
   20 |       6 | m    | m              | s    | u      | 50000 | blue05-em1 | blue05-em2 |            51000 | 
   21 |       7 | m    | m              | s    | u      | 50001 | blue02-em1 | blue02-em3 |            51001 | 
   22 |       8 | m    | m              | s    | u      | 50002 | blue03-em1 | blue03-em1 |            51002 | 
   23 |       9 | m    | m              | s    | u      | 50000 | blue02-em1 | blue02-em2 |            51000 | 
   24 |      10 | m    | m              | s    | u      | 50001 | blue03-em1 | blue03-em3 |            51001 | 
   25 |      11 | m    | m              | s    | u      | 50002 | blue04-em1 | blue04-em1 |            51002 | 
(25 rows)

select gp_segment_id,count(*) from testdata group by 1;
 gp_segment_id | count 
---------------+-------
             0 |     1
             6 |     2
            11 |     1
             1 |     2
             4 |     2
             9 |     1
             2 |     1
             7 |     1
             3 |     1

可以看到虽然我们的表是distributed randomly创建的，但是数据并不是严格按照每个节点一条数据的分布的。

2.kill掉blue05的进程
pkill -9 postgres

3.检查目前的状况

select * from gp_segment_configuration order by 1;
dbid | content | role | preferred_role | mode | status | port  |  hostname  |  address   | replication_port | san_mounts 
------+---------+------+----------------+------+--------+-------+------------+------------+------------------+------------
    1 |      -1 | p    | p              | s    | u      |  5432 | blue01-em1 | blue01-em1 |                  | 
    2 |       0 | p    | p              | s    | u      | 40000 | blue02-em1 | blue02-em1 |            41000 | 
    3 |       1 | p    | p              | s    | u      | 40001 | blue02-em1 | blue02-em2 |            41001 | 
    4 |       2 | p    | p              | c    | u      | 40002 | blue02-em1 | blue02-em3 |            41002 | 
    5 |       3 | p    | p              | s    | u      | 40000 | blue03-em1 | blue03-em1 |            41000 | 
    6 |       4 | p    | p              | c    | u      | 40001 | blue03-em1 | blue03-em2 |            41001 | 
    7 |       5 | p    | p              | s    | u      | 40002 | blue03-em1 | blue03-em3 |            41002 | 
    8 |       6 | p    | p              | c    | u      | 40000 | blue04-em1 | blue04-em1 |            41000 | 
    9 |       7 | p    | p              | s    | u      | 40001 | blue04-em1 | blue04-em2 |            41001 | 
   10 |       8 | p    | p              | s    | u      | 40002 | blue04-em1 | blue04-em3 |            41002 | 
   11 |       9 | m    | p              | s    | d      | 40000 | blue05-em1 | blue05-em1 |            41000 | 
   12 |      10 | m    | p              | s    | d      | 40001 | blue05-em1 | blue05-em2 |            41001 | 
   13 |      11 | m    | p              | s    | d      | 40002 | blue05-em1 | blue05-em3 |            41002 | 
   14 |       0 | m    | m              | s    | u      | 50000 | blue03-em1 | blue03-em2 |            51000 | 
   15 |       1 | m    | m              | s    | u      | 50001 | blue04-em1 | blue04-em3 |            51001 | 
   16 |       2 | m    | m              | s    | d      | 50002 | blue05-em1 | blue05-em1 |            51002 | 
   17 |       3 | m    | m              | s    | u      | 50000 | blue04-em1 | blue04-em2 |            51000 | 
   18 |       4 | m    | m              | s    | d      | 50001 | blue05-em1 | blue05-em3 |            51001 | 
   19 |       5 | m    | m              | s    | u      | 50002 | blue02-em1 | blue02-em1 |            51002 | 
   20 |       6 | m    | m              | s    | d      | 50000 | blue05-em1 | blue05-em2 |            51000 | 
   21 |       7 | m    | m              | s    | u      | 50001 | blue02-em1 | blue02-em3 |            51001 | 
   22 |       8 | m    | m              | s    | u      | 50002 | blue03-em1 | blue03-em1 |            51002 | 
   23 |       9 | p    | m              | c    | u      | 50000 | blue02-em1 | blue02-em2 |            51000 | 
   24 |      10 | p    | m              | c    | u      | 50001 | blue03-em1 | blue03-em3 |            51001 | 
   25 |      11 | p    | m              | c    | u      | 50002 | blue04-em1 | blue04-em1 |            51002 | 
(25 rows)

以上关键字段含义：
role:该节点现在的角色，取值为p(parimary)或m(mirror)
preferred_role:该节点被定义的角色，取值为p(primary)或m(mirror)
mode：主备同步的状态，取值s(synchronized已同步)、r(resyncing正在同步)、c(change logging不同步)
status:判断节点的值，取值为u(up正常运行)和d(down节点失败)

从以上我们可以看出hostname为blue05-em1的41000、41001、41002的同步端口上的原先为主节点角色已经变更为mirror，并且已经down机（进程信息丢失）

4.后续检查：
我们检查数据是否可以查询查询：

select * from testdate; #可以正常查询数据
  insert into testdata select 3,'test'; #可以正常插入
select gp_segment_id,count(*) from testdata group by 1;
 gp_segment_id | count 
---------------+-------
             6 |     2
             1 |     2
            11 |     1
             9 |     1
             4 |     2
             0 |     1
             7 |     1
             3 |     1
             2 |     1

可以使用gpstate -s查看mirror情况

20160816:13:36:42:017605 gpstate:blue01-em1:gpadmin-[INFO]:-Starting gpstate with args: -m
20160816:13:36:42:017605 gpstate:blue01-em1:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.9.0 build 1'
20160816:13:36:42:017605 gpstate:blue01-em1:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.9.0 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Aug  8 2016 05:36:26'
20160816:13:36:42:017605 gpstate:blue01-em1:gpadmin-[INFO]:-Obtaining Segment details from master...
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:--Current GPDB mirror list and status
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:--Type = Spread
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   Mirror       Datadir                               Port    Status              Data Status       
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em2   /home/gpadmin/data/gpdatam1/gpseg0    50000   Passive             Synchronized
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em3   /home/gpadmin/data/gpdatam2/gpseg1    50001   Passive             Synchronized
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[WARNING]:-blue05-em1   /home/gpadmin/data/gpdatam3/gpseg2    50002   Failed                                <<<<<<<<
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em2   /home/gpadmin/data/gpdatam1/gpseg3    50000   Passive             Synchronized
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[WARNING]:-blue05-em3   /home/gpadmin/data/gpdatam2/gpseg4    50001   Failed                                <<<<<<<<
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em1   /home/gpadmin/data/gpdatam3/gpseg5    50002   Passive             Synchronized
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[WARNING]:-blue05-em2   /home/gpadmin/data/gpdatam1/gpseg6    50000   Failed                                <<<<<<<<
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em3   /home/gpadmin/data/gpdatam2/gpseg7    50001   Passive             Synchronized
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em1   /home/gpadmin/data/gpdatam3/gpseg8    50002   Passive             Synchronized
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em2   /home/gpadmin/data/gpdatam1/gpseg9    50000   Acting as Primary   Change Tracking
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em3   /home/gpadmin/data/gpdatam2/gpseg10   50001   Acting as Primary   Change Tracking
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em1   /home/gpadmin/data/gpdatam3/gpseg11   50002   Acting as Primary   Change Tracking
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[WARNING]:-3 segment(s) configured as mirror(s) are acting as primaries
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[WARNING]:-3 segment(s) configured as mirror(s) have failed
20160816:13:36:43:017605 gpstate:blue01-em1:gpadmin-[WARNING]:-3 mirror segment(s) acting as primaries are in change tracking

因此，我们可以断定，blue05的机器down机，节点数据已经转移，备用节点已经启用，正常的业务不受影响，而且数据可以正常插入。

5.修复
要恢复到原来的架构，有两种可能情况，第一种情况，当故障主机启动后，这台主机上的节点会自动启动，当然现在已经都是Mirror节点了，角色是不会切换的，
而且数据是不一致状态。这种情况只需要使用gprecoverseg命令同步一下数据后，就可以切换到原来的架构了。
输入gprecoverseg 然后输入Y

Continue with segment recovery procedure Yy|Nn (default=N):
> y
20160816:13:42:20:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-6 segment(s) to recover
20160816:13:42:20:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Ensuring 6 failed segment(s) are stopped

20160816:13:42:22:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Ensuring that shared memory is cleaned up for stopped segments
updating flat files
20160816:13:42:27:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Updating configuration with new mirrors
20160816:13:42:28:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Updating mirrors
. 
20160816:13:42:29:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Starting mirrors
20160816:13:42:29:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Commencing parallel primary and mirror segment instance startup, please wait...
.. 
20160816:13:42:31:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Process results...
20160816:13:42:31:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Updating configuration to mark mirrors up
20160816:13:42:31:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Updating primaries
20160816:13:42:31:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Commencing parallel primary conversion of 6 segments, please wait...
. 
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Process results...
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Done updating primaries
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-******************************************************************
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Updating segments for resynchronization is completed.
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-For segments updated successfully, resynchronization will continue in the background.
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Use  gpstate -s  to check the resynchronization progress.
20160816:13:42:32:017728 gprecoverseg:blue01-em1:gpadmin-[INFO]:-******************************************************************

按照提示，查看节点信息，这里只检查mirror
gpstate -m

20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-Obtaining Segment details from master...
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:--Current GPDB mirror list and status
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:--Type = Spread
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   Mirror       Datadir                               Port    Status              Data Status    
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em2   /home/gpadmin/data/gpdatam1/gpseg0    50000   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em3   /home/gpadmin/data/gpdatam2/gpseg1    50001   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em1   /home/gpadmin/data/gpdatam3/gpseg2    50002   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em2   /home/gpadmin/data/gpdatam1/gpseg3    50000   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em3   /home/gpadmin/data/gpdatam2/gpseg4    50001   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em1   /home/gpadmin/data/gpdatam3/gpseg5    50002   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em2   /home/gpadmin/data/gpdatam1/gpseg6    50000   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em3   /home/gpadmin/data/gpdatam2/gpseg7    50001   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em1   /home/gpadmin/data/gpdatam3/gpseg8    50002   Passive             Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em2   /home/gpadmin/data/gpdatam1/gpseg9    50000   Acting as Primary   Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em3   /home/gpadmin/data/gpdatam2/gpseg10   50001   Acting as Primary   Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em1   /home/gpadmin/data/gpdatam3/gpseg11   50002   Acting as Primary   Synchronized
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:43:27:017884 gpstate:blue01-em1:gpadmin-[WARNING]:-3 segment(s) configured as mirror(s) are acting as primaries

我们看到数据同步已经完成，但是角色还没有转换过来，需要使用gprecoverseg -r
我们看到数据同步已经完成，但是角色还没有转换过来，需要使用gprecoverseg -r进行角色切换

Continue with segment rebalance procedure Yy|Nn (default=N):
> y
20160816:13:45:24:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Getting unbalanced segments
20160816:13:45:24:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Stopping unbalanced primary segments...
.. 
20160816:13:45:26:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Triggering segment reconfiguration
20160816:13:45:30:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Starting segment synchronization
................. 
20160816:13:45:47:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-******************************************************************
20160816:13:45:47:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-The rebalance operation has completed successfully.
20160816:13:45:47:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-There is a resynchronization running in the background to bring all
20160816:13:45:47:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-segments in sync.
20160816:13:45:47:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-
20160816:13:45:47:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-Use gpstate -e to check the resynchronization progress.
20160816:13:45:47:017935 gprecoverseg:blue01-em1:gpadmin-[INFO]:-******************************************************************

gpstate -e查看同步进程
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-----------------------------------------------------
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-Segment Mirroring Status Report
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-----------------------------------------------------
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-Segment Pairs in Resynchronization
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-   Current Primary   Port    Resync mode   Est. resync progress   Total resync objects   Objects to resync   Data synced   Est. total to sync                      Est. resync end time   Change tracking size   Mirror       Port
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em1        40000   Incremental   100%                   0                      0                   224 kB        Sync complete; awaiting config change                          128 bytes              blue02-em2   50000
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em2        40001   Incremental   100%                   0                      0                   224 kB        Sync complete; awaiting config change                          128 bytes              blue03-em3   50001
20160816:13:46:29:018199 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em3        40002   Incremental   100%                   0                      0                   224 kB        Sync complete; awaiting config change                          128 bytes              blue04-em1   50002

再查看mirror情况
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-Obtaining Segment details from master...
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:--Current GPDB mirror list and status
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:--Type = Spread
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   Mirror       Datadir                               Port    Status    Data Status    
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em2   /home/gpadmin/data/gpdatam1/gpseg0    50000   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em3   /home/gpadmin/data/gpdatam2/gpseg1    50001   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em1   /home/gpadmin/data/gpdatam3/gpseg2    50002   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em2   /home/gpadmin/data/gpdatam1/gpseg3    50000   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em3   /home/gpadmin/data/gpdatam2/gpseg4    50001   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em1   /home/gpadmin/data/gpdatam3/gpseg5    50002   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue05-em2   /home/gpadmin/data/gpdatam1/gpseg6    50000   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em3   /home/gpadmin/data/gpdatam2/gpseg7    50001   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em1   /home/gpadmin/data/gpdatam3/gpseg8    50002   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue02-em2   /home/gpadmin/data/gpdatam1/gpseg9    50000   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue03-em3   /home/gpadmin/data/gpdatam2/gpseg10   50001   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:-   blue04-em1   /home/gpadmin/data/gpdatam3/gpseg11   50002   Passive   Synchronized
20160816:13:47:27:018297 gpstate:blue01-em1:gpadmin-[INFO]:--------------------------------------------------------------

现在查看角色已经转换过来，在用sql验证一下

select * from gp_segment_configuration order by 1;

 dbid | content | role | preferred_role | mode | status | port  |  hostname  |  address   | replication_port | san_mounts 
------+---------+------+----------------+------+--------+-------+------------+------------+------------------+------------
    1 |      -1 | p    | p              | s    | u      |  5432 | blue01-em1 | blue01-em1 |                  | 
    2 |       0 | p    | p              | s    | u      | 40000 | blue02-em1 | blue02-em1 |            41000 | 
    3 |       1 | p    | p              | s    | u      | 40001 | blue02-em1 | blue02-em2 |            41001 | 
    4 |       2 | p    | p              | s    | u      | 40002 | blue02-em1 | blue02-em3 |            41002 | 
    5 |       3 | p    | p              | s    | u      | 40000 | blue03-em1 | blue03-em1 |            41000 | 
    6 |       4 | p    | p              | s    | u      | 40001 | blue03-em1 | blue03-em2 |            41001 | 
    7 |       5 | p    | p              | s    | u      | 40002 | blue03-em1 | blue03-em3 |            41002 | 
    8 |       6 | p    | p              | s    | u      | 40000 | blue04-em1 | blue04-em1 |            41000 | 
    9 |       7 | p    | p              | s    | u      | 40001 | blue04-em1 | blue04-em2 |            41001 | 
   10 |       8 | p    | p              | s    | u      | 40002 | blue04-em1 | blue04-em3 |            41002 | 
   11 |       9 | p    | p              | s    | u      | 40000 | blue05-em1 | blue05-em1 |            41000 | 
   12 |      10 | p    | p              | s    | u      | 40001 | blue05-em1 | blue05-em2 |            41001 | 
   13 |      11 | p    | p              | s    | u      | 40002 | blue05-em1 | blue05-em3 |            41002 | 
   14 |       0 | m    | m              | s    | u      | 50000 | blue03-em1 | blue03-em2 |            51000 | 
   15 |       1 | m    | m              | s    | u      | 50001 | blue04-em1 | blue04-em3 |            51001 | 
   16 |       2 | m    | m              | s    | u      | 50002 | blue05-em1 | blue05-em1 |            51002 | 
   17 |       3 | m    | m              | s    | u      | 50000 | blue04-em1 | blue04-em2 |            51000 | 
   18 |       4 | m    | m              | s    | u      | 50001 | blue05-em1 | blue05-em3 |            51001 | 
   19 |       5 | m    | m              | s    | u      | 50002 | blue02-em1 | blue02-em1 |            51002 | 
   20 |       6 | m    | m              | s    | u      | 50000 | blue05-em1 | blue05-em2 |            51000 | 
   21 |       7 | m    | m              | s    | u      | 50001 | blue02-em1 | blue02-em3 |            51001 | 
   22 |       8 | m    | m              | s    | u      | 50002 | blue03-em1 | blue03-em1 |            51002 | 
   23 |       9 | m    | m              | s    | u      | 50000 | blue02-em1 | blue02-em2 |            51000 | 
   24 |      10 | m    | m              | s    | u      | 50001 | blue03-em1 | blue03-em3 |            51001 | 
   25 |      11 | m    | m              | s    | u      | 50002 | blue04-em1 | blue04-em1 |            51002 |

再检查下之前停掉的blueo5的进程，ps -ef|grep postgres发现64个进程已经启动了。

Greenplum带优化器的源码编译、离线打包，部署和TPC-DS性能和并发测试
建模分析师胡选来
04-13 1173
************************编译************************ centos 7, raid5, 文件系统xfs，xfs挂载参数：defaults,allocsize=16m,inode64,noatime //安装gp依赖库 yum install -y \ apr-devel \ byacc \ bison \ bzip2...
Greenplum Database 6（开源版） 安装升级卸载及日常维护手册
weixin_45428187的博客
08-06 1737
Greenplum Database 6（开源版） 安装升级卸载及日常维护手册
GPDB 并行加载测试
Gtlions Tracker
12-12 1947
测试文件信息 10G Dec 12 14:10 A1 11G Dec 12 14:32 A2 10G Dec 12 14:10 B1 11G Dec 12 14:35 B2 GPFDIST 方案一 单台服务器 drop table if exists host_1; drop EXTERNAL TABLE if exists ip_session_gpfs_ext_1_host; dro
Cypress系列（75）- spread() 命令详解
qq_33801641的博客
11-20 303
如果想从头学起Cypress，可以看下面的系列文章哦 https://www.cnblogs.com/poloyy/category/1768839.html 作用 将数组拆分为多个参数 有点像 py 里面的 *array 语法格式 .spread(callbackFn) .spread(options, callbackFn) callbackFn 回调函数 将数组拆分后作为...
GP部署方案考虑（1）
11-26 421
我们以2台交换机，1个Master Host，4个Segment host为例来阐述。 在每个Segment Host（即PC服务器节点）上4张网卡，配置4个segment（即每个PC服务器节点上的gp实例），每个segmen...
GP failover，primary和mirror切换实验
我的Oracle DBA之路
03-09 1638
GP failover，primary和mirror切换实验 http://blog.sina.com.cn/s/blog_9869114e0101k1nc.html一、恢复失败的segment出现segment节点down，恢复GP的思路：if"segment down" thencase "determine case(errer,message,log,gpstate and so on)"...
10. Greenplum高可用架构
murkey的专栏
05-01 979
10. Greenplum高可用架构与数据持久化论述 Greenplum数据库系统的高可用可以通过提供容错硬件平台实现，可以通过启用Greenplum数据库高可用特性实现，也可以通过执行定期监控和运维作业来确保整个系统所有组件保持健康来实现。 硬件平台的最终故障，可能因为常见的持久运行故障或非预期的运行环境。异常断电会导致组件临时不可用。系统可以通过为可能故障的节点配置冗余备份节点来保...
部署greenplum集群详细教程
最新发布
weixin_57900254的博客
08-21 1472
这里使用1个master，2个segment的集群，ip为：其中1192.168.1.171为master，192.168.1.172为备用节点，其余为segment。注意：PGPORT指的是你安装greenplum数据库的端口号。
【GP5安装配置】 Greenplum5.23 安装手记
热门推荐
LiangHC
12-21 1万+
作者：lianghc 时间：20191221 目录 作者：lianghc 时间：20191221 1.安装前准备 2. 安装步骤概述 2.1 常规安装 2.1 非常规安装法(先安装，再改参数) 3. 系统参数修改清单 3.1 /etc/host 3.2 /etc/sysctl.conf 3.2.1 /etc/sysctl.conf 原文件内容 3.3 /etc/secu...
greenplum如何删除segment节点
DreamDB的专栏
04-20 3131
环境信息： Red Hat Enterprise Linux Server release 7.5 (Maipo) Greenplum Database 5.16.0 [gpadmin@rhmdw gpadata]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdo...
Greenplum概念学习——节点分布模式：grouped、spread
肥叔菌的博客
01-12 3784
greenplum的两种节点分布模式 (6台主机，每台4个segment，两两primary、mirror) ①grouped mirror模式：(grouped模式，主机的mirror节点全部放在下一个主机上) ②spread mirror模式： (spread模式,主机的第一个mirror在下个主机,第二个mirror在次下个主机,第三mirror在次次下个主机…) 初始化的mirror模式： 1）初始化为grouped模式 在部署配置gp的过程中，执行初始化命令：gpinitsystem ，默认的
Greenplum实战--检查集群状态gpstate
murkey的专栏
04-19 4174
查看进程命令 $gpssh -f /home/gpadmin/gpconfig/all_host -e "ps -eaf|grep green" [ mdw] ps -eaf|grep green [ mdw] gpadmin 2601 1 0 01:04 ? 00:00:00 /usr/local/greenplum-db-5.10.2/bi...
Greenplum学习12--添加mirror节点
Rorschach的博客
01-11 3940
在安装部署greenplum的时候，没有在配置文件加入mirror节点做primary节点的同步备份，会造成一些问题，该篇就是如何在没有mirror节点的情况下添加mirror
windows 安装 greenplum-loader
happyzxs的博客
11-28 4567
1.先到官网下载，地址地址：https://network.pivotal.io/products/pivotal-gpdb 2.安装python(一定要安装2.5.4版本)地：https://www.python.org/downloads/release/python-2714 将python添加到环境变量，环境变量为python安装路径。3.安装yam（与python版本要匹配） 官网上没
Greenplum学习8--节点分布模式：grouped、spread
Rorschach的博客
10-24 4107
对于Greenplum的集群节点的分布的两种模式，spread和grouped
敏捷测试之一：敏捷测试的核心
Spread_learning的博客
04-08 1255
今天在一个平台上学习的课程记录如下，供参考学习： 一：传统测试和敏捷测试的区别： 传统测试： 独立的测试部门 测试工作主要由测试人员承担 详尽的测试用例文档 集中的回归测试 发现更多的BUG 敏捷测试 伴随着着敏捷开发过程的所有质量相关活动 敏捷测试不能独立存在，不是一种类型或方法 敏捷测试不仅是测试人员的工作，是团队的活动 抛开敏捷开发谈敏捷测试没有意义 二、敏捷测试的目标 发现更多的bug-...
ERROR: invalid memory alloc request size 1111005384
数据人
04-27 4449
一般出现此问题多是由于调整系统参数值为一个错误的值导致的。 恢复参数默认值可以使用gpconfig来批量设置master和segmentgpconfig -r <参数> -- 把参数重置成默认值如果想查询参数的取值范围，可以通过下面的方法获取psql postgres postgres=#select * from pg_settings where name ~ '参数名'; --可看到
ERROR: insufficient memory reserved for statement tuplesort_mk.h:115
数据人
04-27 3664
这个错误是个困扰我很长时间的问题，我发生此问题在进行大数据导入的时候，开始发现此错误提示的时候，我们都会从内存调整的角度去考虑，比如调整内存相关的参数，比如我按照如下的调整。gpconfig -c max_statement_mem -v 10GB #单个查询最大内存 gpconfig -c max_work_mem -v 10GB #与上面相关 gpconfig -c stateme
relation "public.***" contains more than "max_fsm_pages" pages with useful free space
数据人
04-27 2660
有时我们在操作大表的时候会发生relation “public.*” contains more than “max_fsm_pages” pages with useful free space的错误，其实这个错误和max_fsm_pages参数有关。max_fsm_pages必须大于 16 * max_fsm_relations，且max_fsm_pages最小必须为100,看出当max_fsm
gpdb CREATE DATABASE 未找到命令
12-06
如果在gpdb中使用CREATE DATABASE命令未找到，则可能是由于以下原因之一： 1. 没有足够的权限执行该命令。 2. CREATE DATABASE命令不是gpdb支持的命令。 如果是第一种情况，您需要使用具有足够权限的用户登录到...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值