greenplum如何删除segment节点

本文详细记录了在Red Hat Enterprise Linux Server 7.5上运行Greenplum Database 5.16.0时,如何删除segment节点的过程。内容包括检查集群状态、进行数据库备份、删除节点及验证恢复等关键步骤。删除节点需按照content从大到小的顺序进行,并确保删除后的数据能被正确恢复。
摘要由CSDN通过智能技术生成

环境信息:

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.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.15.201  rhmdw
192.168.15.202  rhsdw1
192.168.15.203  rhsdw2
192.168.15.205  rhsdw03
192.168.15.206  rhsdw04

gp官网也未指出如何删除节点,网上有多个删除方式,针对于删除方式进行验证,在进行删除时需要注意以下两点内容:
1、删除节点的content必须是从大到小删除,如果存在单个content集群将会启动失败。
2、删除节点后必须将问题节点的内容恢复到其他节点。

测试过程删除rhsdw03和rhsdw04节点
集群状态查看:
[gpadmin@rhmdw ~]$ gpstate -m
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-Starting gpstate with args: -m
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 5.16.0 build commit:23cec7df0406d69d6552a4bbb77035dba4d7dd44'
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.3.23 (Greenplum Database 5.16.0 build commit:23cec7df0406d69d6552a4bbb77035dba4d7dd44) on x86_64-pc-linux-gnu, compiled by GCC gcc (GCC) 6.2.0, 64-bit compiled on Jan 16 2019 02:32:15'
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:--------------------------------------------------------------
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:--Current GPDB mirror list and status
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:--Type = Spread
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:--------------------------------------------------------------
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-   Mirror    Datadir                    Port   Status    Data Status    
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw2    /gp/gpdata/mirror/gpseg0   7000   Passive   Synchronized
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw1    /gp/gpdata/mirror/gpseg1   7000   Passive   Synchronized
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw03   /gp/gpdata/mirror/gpseg2   7000   Passive   Synchronized
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw04   /gp/gpdata/mirror/gpseg3   7000   Passive   Synchronized
20190418:17:58:44:025396 gpstate:rhmdw:gpadmin-[INFO]:--------------------------------------------------------------
[gpadmin@rhmdw ~]$ psql -d postgres
psql (8.3.23)
Type "help" for help.


postgres=# select * from gp_segment_configuration order by dbid;
 dbid | content | role | preferred_role | mode | status | port | hostname | address | replication_port
------+---------+------+----------------+------+--------+------+----------+---------+------------------
    1 |      -1 | p    | p              | s    | u      | 5432 | rhmdw    | rhmdw   |                 
    2 |       0 | p    | p              | s    | u      | 6000 | rhsdw1   | rhsdw1  |             9000
    3 |       1 | p    | p              | s    | u      | 6000 | rhsdw2   | rhsdw2  |             9000
    4 |       0 | m    | m              | s    | u      | 7000 | rhsdw2   | rhsdw2  |             8000
    5 |       1 | m    | m              | s    | u      | 7000 | rhsdw1   | rhsdw1  |             8000
    6 |      -1 | m    | m              | s    | u      | 5432 | rhsdw1   | rhsdw1  |                 
    7 |       2 | p    | p              | s    | u      | 6000 | rhsdw03  | rhsdw03 |             9000
    8 |       3 | p    | p              | s    | u      | 6000 | rhsdw04  | rhsdw04 |             9000
    9 |       2 | m    | m              | s    | u      | 7000 | rhsdw03  | rhsdw03 |             8000
   10 |       3 | m    | m              | s    | u      | 7000 | rhsdw04  | rhsdw04 |             8000
(10 rows)

数据库再做重大操作之前数据库备份是必须的。查看数据库信息,备份所有数据库:
postgres=# \l
                  List of databases
   Name    |  Owner  | Encoding |  Access privileges  
-----------+---------+----------+---------------------
 gaoyc     | gpadmin | UTF8     |
 gpperfmon | gpadmin | UTF8     | gpadmin=CTc/gpadmin
                                : =c/gpadmin
 postgres  | gpadmin | UTF8     |
 template0 | gpadmin | UTF8     | =c/gpadmin          
                                : gpadmin=CTc/gpadmin
 template1 | gpadmin | UTF8     | =c/gpadmin          
                                : gpadmin=CTc/gpadmin
(5 rows)


[gpadmin@rhmdw ~]$ gp_dump --gp-d=/gp/gpdata  gaoyc
20190418:18:08:09|gp_dump-[INFO]:-Read params: <empty>
20190418:18:08:09|gp_dump-[INFO]:-Command line options analyzed.
20190418:18:08:09|gp_dump-[INFO]:-Connecting to master database on host localhost port 5432 database gaoyc.
20190418:18:08:09|gp_dump-[INFO]:-Reading Greenplum Database configuration info from master database.
20190418:18:08:09|gp_dump-[INFO]:-Preparing to dump the following segments:
20190418:18:08:09|gp_dump-[INFO]:-Segment 3 (dbid 8)
20190418:18:08:09|gp_dump-[INFO]:-Segment 2 (dbid 7)
20190418:18:08:09|gp_dump-[INFO]:-Segment 1 (dbid 3)
20190418:18:08:09|gp_dump-[INFO]:-Segment 0 (dbid 2)
20190418:18:08:09|gp_dump-[INFO]:-Master (dbid 1)
20190418:18:08:09|gp_dump-[INFO]:-Starting a transaction on master database gaoyc.
20190418:18:08:09|gp_dump-[INFO]:-Getting a lock on pg_class in database gaoyc.
20190418:18:08:09|GetTimestampKey-[INFO]:-Timestamp key is generated as it is not provided by the user.
20190418:18:08:09|gp_dump-[INFO]:-About to spin off 5 threads with timestamp key 20190418180809
20190418:18:08:09|gp_dump-[INFO]:-Creating thread to backup dbid 8: host rhsdw04 port 6000 database gaoyc
20190418:18:08:09|gp_dump-[INFO]:-Creating thread to backup dbid 7: host rhsdw03 port 6000 database gaoyc
20190418:18:08:09|gp_dump-[INFO]:-Creating thread to backup dbid 3: host rhsdw2 port 6000 database gaoyc
20190418:18:08:09|gp_dump-[INFO]:-Creating thread to backup dbid 2: host rhsdw1 port 6000 database gaoyc
20190418:18:08:09|gp_dump-[INFO]:-Creating thread to backup dbid 1: host rhmdw port 5432 database gaoyc
20190418:18:08:09|gp_dump-[INFO]:-Waiting for remote gp_dump_agent processes to start transactions in serializable isolation level
20190418:18:08:09|gp_dump-[INFO]:-Listening for messages from server on dbid 8 connection
20190418:18:08:09|gp_dump-[INFO]:-Successfully launched Greenplum Database backup on dbid 8 server
20190418:18:08:09|gp_dump-[INFO]:-Listening for messages from server on dbid 7 connection
20190418:18:08:09|gp_dump-[INFO]:-Successfully launched Greenplum Database backup on dbid 7 server
20190418:18:08:09|gp_dump-[INFO]:-Listening for messages from server on dbid 2 connection
20190418:18:08:09|gp_dump-[INFO]:-Successfully launched Greenplum Database backup on dbid 2 server
20190418:18:08:09|gp_dump-[INFO]:-Listening for messages from server on dbid 3 connection
20190418:18:08:09|gp_dump-[INFO]:-Successfully launched Greenplum Database backup on dbid 3 server
20190418:18:08:09|gp_dump-[INFO]:-Listening for messages from server on dbid 1 connection
20190418:18:08:12|gp_dump-[INFO]:-backup succeeded for dbid 7 on host rhsdw03
20190418:18:08:12|gp_dump-[INFO]:-Successfully launched Greenplum Database backup on dbid 1 server
20190418:18:08:12|gp_dump-[INFO]:-backup succeeded for dbid 1 on host rhmdw
20190418:18:08:12|gp_dump-[INFO]:-backup succeeded for dbid 2 on host rhsdw1
20190418:18:08:12|gp_dump-[INFO]:-backup succeeded for dbid 8 on host rhsdw04
20190418:18:08:12|gp_dump-[INFO]:-All remote gp_dump_agent processes have began tr

  • 2
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值