GreenPlum删除节点

最新推荐文章于 2023-04-06 18:16:54 发布
原创 最新推荐文章于 2023-04-06 18:16:54 发布 · 1.4k 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文详细介绍了如何在GreenPlum数据库中删除指定节点，包括数据库状态检查、停止数据库、从配置表中删除节点信息及重启数据库的全过程。

GreenPlum删除节点

查看数据库当前状态
[gpadmin@server04 greenplum]$ gpstate
20191106:23:08:35:006912 gpstate:server04:gpadmin-[INFO]:-Starting gpstate with args: 
20191106:23:08:36:006912 gpstate:server04:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 5.21.3 build commit:3d56d131a82082e5f1c69ecee50177f6484ed6a4'
20191106:23:08:36:006912 gpstate:server04:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.3.23 (Greenplum Database 5.21.3 build commit:3d56d131a82082e5f1c69ecee50177f6484ed6a4) on x86_64-pc-linux-gnu, compiled by GCC gcc (GCC) 6.2.0, 64-bit compiled on Aug 29 2019 17:19:21'
20191106:23:08:36:006912 gpstate:server04:gpadmin-[INFO]:-Obtaining Segment details from master...
20191106:23:08:36:006912 gpstate:server04:gpadmin-[INFO]:-Gathering data from segments...
.. 
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-Greenplum instance status summary
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-----------------------------------------------------
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Master instance                                = Active
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Master standby                                 = No master standby configured
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total segment instance count from metadata     = 15
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-----------------------------------------------------
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Primary Segment Status
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-----------------------------------------------------
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total primary segments                         = 15
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total primary segment valid (at master)        = 15
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total primary segment failures (at master)     = 0
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number of postmaster.pid files missing   = 0
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number of postmaster.pid files found     = 15
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs missing    = 0
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs found      = 15
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number of /tmp lock files missing        = 0
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number of /tmp lock files found          = 15
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number postmaster processes missing      = 0
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Total number postmaster processes found        = 15
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-----------------------------------------------------
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Mirror Segment Status
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-----------------------------------------------------
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-   Mirrors not configured on this array
20191106:23:08:38:006912 gpstate:server04:gpadmin-[INFO]:-----------------------------------------------------
​
关闭当前数据库
[gpadmin@server04 greenplum]$ gpstop -M fast
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-Starting gpstop with args: -M fast
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-Gathering information and validating the environment...
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-Obtaining Segment details from master...
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-Greenplum Version: 'postgres (Greenplum Database) 5.21.3 build commit:3d56d131a82082e5f1c69ecee50177f6484ed6a4'
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:---------------------------------------------
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-Master instance parameters
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:---------------------------------------------
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Master Greenplum instance process active PID   = 16688
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Database                                       = template1
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Master port                                    = 5432
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Master directory                               = /data1/greenplum/data/master/gpseg-1
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Shutdown mode                                  = fast
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Timeout                                        = 120
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Shutdown Master standby host                   = Off
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:---------------------------------------------
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-Segment instances that will be shutdown:
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:---------------------------------------------
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   Host               Datadir                                 Port   Status
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server04.novalocal   /data1/greenplum/data/primary/gpseg0    6000   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server04.novalocal   /data1/greenplum/data/primary/gpseg1    6001   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server04.novalocal   /data1/greenplum/data/primary/gpseg2    6002   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server12.novalocal   /data1/greenplum/data/primary/gpseg3    6000   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server12.novalocal   /data1/greenplum/data/primary/gpseg4    6001   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server12.novalocal   /data1/greenplum/data/primary/gpseg5    6002   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server14.novalocal   /data1/greenplum/data/primary/gpseg6    6000   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server14.novalocal   /data1/greenplum/data/primary/gpseg7    6001   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server14.novalocal   /data1/greenplum/data/primary/gpseg8    6002   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server16.novalocal   /data1/greenplum/data/primary/gpseg9    6000   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server16.novalocal   /data1/greenplum/data/primary/gpseg10   6001   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server16.novalocal   /data1/greenplum/data/primary/gpseg11   6002   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server04.novalocal   /data1/greenplum/data/primary/gpseg12   6003   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server04.novalocal   /data1/greenplum/data/primary/gpseg13   6004   u
20191106:23:10:58:008777 gpstop:server04:gpadmin-[INFO]:-   server04.novalocal   /data1/greenplum/data/primary/gpseg14   6005   u
​
Continue with Greenplum instance shutdown Yy|Nn (default=N):
> y
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-There are 5 connections to the database
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-Commencing Master instance shutdown with mode='fast'
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-Master host=172.16.0.4
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-Detected 5 connections to database
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-Switching to WAIT mode
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-Will wait for shutdown to complete, this may take some time if
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-there are a large number of active complex transactions, please wait...
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-Commencing Master instance shutdown with mode=fast
20191106:23:10:59:008777 gpstop:server04:gpadmin-[INFO]:-Master segment instance directory=/data1/greenplum/data/master/gpseg-1
20191106:23:11:00:008777 gpstop:server04:gpadmin-[INFO]:-Attempting forceful termination of any leftover master process
20191106:23:11:00:008777 gpstop:server04:gpadmin-[INFO]:-Terminating processes for segment /data1/greenplum/data/master/gpseg-1
20191106:23:11:00:008777 gpstop:server04:gpadmin-[INFO]:-No standby master host configured
20191106:23:11:00:008777 gpstop:server04:gpadmin-[INFO]:-Targeting dbid [2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17] for shutdown
20191106:23:11:00:008777 gpstop:server04:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait...
20191106:23:11:00:008777 gpstop:server04:gpadmin-[INFO]:-0.00% of jobs completed
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-100.00% of jobs completed
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-----------------------------------------------------
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-   Segments stopped successfully      = 15
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-   Segments with errors during stop   = 0
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-----------------------------------------------------
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-Successfully shutdown 15 of 15 segment instances 
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-Database successfully shutdown with no errors reported
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-Cleaning up leftover gpmmon process
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-No leftover gpmmon process found
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-Cleaning up leftover gpsmon processes
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-No leftover gpsmon processes on some hosts. not attempting forceful termination on these hosts
20191106:23:11:03:008777 gpstop:server04:gpadmin-[INFO]:-Cleaning up leftover shared memory
​
以管理模式启动数据库
[gpadmin@server04 greenplum]$ gpstart -m
20191106:23:12:11:009614 gpstart:server04:gpadmin-[INFO]:-Starting gpstart with args: -m
20191106:23:12:11:009614 gpstart:server04:gpadmin-[INFO]:-Gathering information and validating the environment...
20191106:23:12:11:009614 gpstart:server04:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 5.21.3 build commit:3d56d131a82082e5f1c69ecee50177f6484ed6a4'
20191106:23:12:11:009614 gpstart:server04:gpadmin-[INFO]:-Greenplum Catalog Version: '301705051'
20191106:23:12:11:009614 gpstart:server04:gpadmin-[INFO]:-Master-only start requested in configuration without a standby master.
​
Continue with master-only startup Yy|Nn (default=N):
> y
20191106:23:12:13:009614 gpstart:server04:gpadmin-[INFO]:-Starting Master instance in admin mode
20191106:23:12:15:009614 gpstart:server04:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20191106:23:12:15:009614 gpstart:server04:gpadmin-[INFO]:-Obtaining Segment details from master...
20191106:23:12:15:009614 gpstart:server04:gpadmin-[INFO]:-Setting new master era
20191106:23:12:15:009614 gpstart:server04:gpadmin-[INFO]:-Master Started...
登录管理数据库
PGOPTIONS="-c gp_session_role=utility" psql -d postgres

删除segment

 select * from gp_segment_configuration;
 
 postgres=#  select * from gp_segment_configuration;
 dbid | content | role | preferred_role | mode | status | port |     hostname     |  address   | replication_port 
------+---------+------+----------------+------+--------+------+------------------+------------+------------------
    2 |       0 | p    | p              | s    | u      | 6000 | server04.novalocal | sdw0       |                 
    5 |       3 | p    | p              | s    | u      | 6000 | server12.novalocal | sdw1       |                 
    8 |       6 | p    | p              | s    | u      | 6000 | server14.novalocal | sdw2       |                 
   11 |       9 | p    | p              | s    | u      | 6000 | server16.novalocal | sdw3       |                 
    3 |       1 | p    | p              | s    | u      | 6001 | server04.novalocal | sdw0       |                 
    6 |       4 | p    | p              | s    | u      | 6001 | server12.novalocal | sdw1       |                 
    9 |       7 | p    | p              | s    | u      | 6001 | server14.novalocal | sdw2       |                 
   12 |      10 | p    | p              | s    | u      | 6001 | server16.novalocal | sdw3       |                 
    4 |       2 | p    | p              | s    | u      | 6002 | server04.novalocal | sdw0       |                 
    7 |       5 | p    | p              | s    | u      | 6002 | server12.novalocal | sdw1       |                 
   10 |       8 | p    | p              | s    | u      | 6002 | server14.novalocal | sdw2       |                 
   13 |      11 | p    | p              | s    | u      | 6002 | server16.novalocal | sdw3       |                 
   15 |      12 | p    | p              | s    | u      | 6003 | server04.novalocal | sdw0       |                 
   16 |      13 | p    | p              | s    | u      | 6004 | server04.novalocal | sdw0       |                 
   17 |      14 | p    | p              | s    | u      | 6005 | server04.novalocal | sdw0       |                 
    1 |      -1 | p    | p              | s    | u      | 5432 | 172.16.0.4       | 172.16.0.4 |                 
(16 rows)
​
postgres=#  select * from gp_segment_configuration where hostname='server04.novalocal';
 dbid | content | role | preferred_role | mode | status | port |     hostname     | address | replication_port 
------+---------+------+----------------+------+--------+------+------------------+---------+------------------
    2 |       0 | p    | p              | s    | u      | 6000 | server04.novalocal | sdw0    |                 
    3 |       1 | p    | p              | s    | u      | 6001 | server04.novalocal | sdw0    |                 
    4 |       2 | p    | p              | s    | u      | 6002 | server04.novalocal | sdw0    |                 
   15 |      12 | p    | p              | s    | u      | 6003 | server04.novalocal | sdw0    |                 
   16 |      13 | p    | p              | s    | u      | 6004 | server04.novalocal | sdw0    |                 
   17 |      14 | p    | p              | s    | u      | 6005 | server04.novalocal | sdw0    |                 
(6 rows)
​
postgres=#  select * from gp_segment_configuration where hostname!='server04.novalocal';
 dbid | content | role | preferred_role | mode | status | port |     hostname     |  address   | replication_port 
------+---------+------+----------------+------+--------+------+------------------+------------+------------------
    5 |       3 | p    | p              | s    | u      | 6000 | server12.novalocal | sdw1       |                 
    8 |       6 | p    | p              | s    | u      | 6000 | server14.novalocal | sdw2       |                 
   11 |       9 | p    | p              | s    | u      | 6000 | server16.novalocal | sdw3       |                 
    6 |       4 | p    | p              | s    | u      | 6001 | server12.novalocal | sdw1       |                 
    9 |       7 | p    | p              | s    | u      | 6001 | server14.novalocal | sdw2       |                 
   12 |      10 | p    | p              | s    | u      | 6001 | server16.novalocal | sdw3       |                 
    7 |       5 | p    | p              | s    | u      | 6002 | server12.novalocal | sdw1       |                 
   10 |       8 | p    | p              | s    | u      | 6002 | server14.novalocal | sdw2       |                 
   13 |      11 | p    | p              | s    | u      | 6002 | server16.novalocal | sdw3       |                 
    1 |      -1 | p    | p              | s    | u      | 5432 | 172.16.0.4       | 172.16.0.4 | 
    
    
    postgres=# select * from pg_filespace_entry ;
 fsefsoid | fsedbid |              fselocation              
----------+---------+---------------------------------------
     3052 |       2 | /data1/greenplum/data/primary/gpseg0
     3052 |       5 | /data1/greenplum/data/primary/gpseg3
     3052 |       8 | /data1/greenplum/data/primary/gpseg6
     3052 |      11 | /data1/greenplum/data/primary/gpseg9
     3052 |       3 | /data1/greenplum/data/primary/gpseg1
     3052 |       6 | /data1/greenplum/data/primary/gpseg4
     3052 |       9 | /data1/greenplum/data/primary/gpseg7
     3052 |      12 | /data1/greenplum/data/primary/gpseg10
     3052 |       4 | /data1/greenplum/data/primary/gpseg2
     3052 |       7 | /data1/greenplum/data/primary/gpseg5
     3052 |      10 | /data1/greenplum/data/primary/gpseg8
     3052 |      13 | /data1/greenplum/data/primary/gpseg11
     3052 |      15 | /data1/greenplum/data/primary/gpseg12
     3052 |      16 | /data1/greenplum/data/primary/gpseg13
     3052 |      17 | /data1/greenplum/data/primary/gpseg14
     3052 |       1 | /data1/greenplum/data/master/gpseg-1
​
设置操作权限
set allow_system_table_mods='dml';
删除节点
delete from gp_segment_configuration where dbid in (2,3,4,15,16,17);
delete from pg_filespace_entry where fsedbid in (2,3,4,15,16,17);  
postgres=#  select * from gp_segment_configuration;
 dbid | content | role | preferred_role | mode | status | port |     hostname     |  address   | replication_port 
------+---------+------+----------------+------+--------+------+------------------+------------+------------------
    5 |       3 | p    | p              | s    | u      | 6000 | server12.novalocal | sdw1       |                 
    8 |       6 | p    | p              | s    | u      | 6000 | server14.novalocal | sdw2       |                 
   11 |       9 | p    | p              | s    | u      | 6000 | server16.novalocal | sdw3       |                 
    6 |       4 | p    | p              | s    | u      | 6001 | server12.novalocal | sdw1       |                 
    9 |       7 | p    | p              | s    | u      | 6001 | server14.novalocal | sdw2       |                 
   12 |      10 | p    | p              | s    | u      | 6001 | server16.novalocal | sdw3       |                 
    7 |       5 | p    | p              | s    | u      | 6002 | server12.novalocal | sdw1       |                 
   10 |       8 | p    | p              | s    | u      | 6002 | server14.novalocal | sdw2       |                 
   13 |      11 | p    | p              | s    | u      | 6002 | server16.novalocal | sdw3       |                 
    1 |      -1 | p    | p              | s    | u      | 5432 | 172.16.0.4       | 172.16.0.4 |
gpstart报错
gpstop -m
​
[gpadmin@server04 greenplum]$ gpstart
20191106:23:33:24:019409 gpstart:server04:gpadmin-[INFO]:-Starting gpstart with args: 
20191106:23:33:24:019409 gpstart:server04:gpadmin-[INFO]:-Gathering information and validating the environment...
20191106:23:33:25:019409 gpstart:server04:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 5.21.3 build commit:3d56d131a82082e5f1c69ecee50177f6484ed6a4'
20191106:23:33:25:019409 gpstart:server04:gpadmin-[INFO]:-Greenplum Catalog Version: '301705051'
20191106:23:33:25:019409 gpstart:server04:gpadmin-[INFO]:-Starting Master instance in admin mode
20191106:23:33:26:019409 gpstart:server04:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20191106:23:33:26:019409 gpstart:server04:gpadmin-[INFO]:-Obtaining Segment details from master...
20191106:23:33:26:019409 gpstart:server04:gpadmin-[INFO]:-Setting new master era
20191106:23:33:26:019409 gpstart:server04:gpadmin-[INFO]:-Master Started...
20191106:23:33:26:019409 gpstart:server04:gpadmin-[CRITICAL]:-gpstart failed. (Reason=''NoneType' object has no attribute 'hostname'') exiting...
​
联系节点
postgres=# update gp_segment_configuration set content=content-3 where content!=-1;
ERROR:  operator does not exist: smallint !=- integer
LINE 1: ...gment_configuration set content=content-3 where content!=-1;
                                                                  ^
HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.
postgres=# update gp_segment_configuration set content=content-3 where dbid!=1;
UPDATE 9
postgres=# select * from gp_segment_configuration;
 dbid | content | role | preferred_role | mode | status | port |     hostname     |  address   | replication_port 
------+---------+------+----------------+------+--------+------+------------------+------------+------------------
    1 |      -1 | p    | p              | s    | u      | 5432 | 172.16.0.4       | 172.16.0.4 |                 
    5 |       0 | p    | p              | s    | u      | 6000 | server12.novalocal | sdw1       |                 
    8 |       3 | p    | p              | s    | u      | 6000 | server14.novalocal | sdw2       |                 
   11 |       6 | p    | p              | s    | u      | 6000 | server16.novalocal | sdw3       |                 
    6 |       1 | p    | p              | s    | u      | 6001 | server12.novalocal | sdw1       |                 
    9 |       4 | p    | p              | s    | u      | 6001 | server14.novalocal | sdw2       |                 
   12 |       7 | p    | p              | s    | u      | 6001 | server16.novalocal | sdw3       |                 
    7 |       2 | p    | p              | s    | u      | 6002 | server12.novalocal | sdw1       |                 
   10 |       5 | p    | p              | s    | u      | 6002 | server14.novalocal | sdw2       |                 
   13 |       8 | p    | p              | s    | u      | 6002 | server16.novalocal | sdw3       |
重启节点
gpstop -m
gpstart
Explorren
关注
Greenplum移除节点
weixin_34101229的博客
05-16 1552
基于某某原因，我们的Greenplum需要卸载一个节点（测试环境的Greenplum集群），由于该集群使用了很久，里面有许多开发所需要的数据，所以在卸掉一个节点后，还要保证数据不会丢失。 经过搜索，在以下站点找到了解决方案1）https://gp-docs-cn.github.io/docs/admin_guide/managing/restore-diff-system.html 2）https...
Deepgreen/Greenplum删除节点步骤
weixin_34279184的博客
08-16 222
Greenplum和Deepgreen官方都没有给出删除节点的方法和建议，但实际上，我们可以对节点进行删除。由于不确定性，删除节点极有可能导致其他的问题，所以还行做好备份，谨慎而为。下面是具体的步骤： 1.查看数据库当前状态（12个实例） [gpadmin@sdw1 ~]$ gpstate 20170816:12:53:25:097578 gpstate...
greenplum的扩容（4）-删除数据节点
aabc012的博客
05-12 4029
greenplum中的数据节点也是可以删除减少的。 现删除增加的1组主备节点。
从greenplum集群中移除节点，并用串行恢复的方法将删除节点的数据重分布到剩余节点...
01-07 742
昨天在把GP数据库从单机装的3.3.6版本升级到4.0.4版本时，老报内存不足的问题，考虑到4.0.4对内存的要求更高（目前虚拟机配的是2G内存），想删除4个节点(原来有8个节点)试试，以节省内存。 在...
Greenplum删除segment节点
曾经是个DBA
09-28 7049
1 备份数据库 [gpadmin@hadoop02 ~]$ gp_dump --gp-d=/home/gpadmin/backup tutorial 20160928:14:41:34|gp_dump-[INFO]:-Read params: 20160928:14:41:34|gp_dump-[INFO]:-Command line options analyzed. 20160928:14
greenplum如何删除segment节点
DreamDB的专栏
04-20 3165
环境信息： 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清除mirror
12-03
在执行任何破坏性操作之前，必须备份Master节点的数据目录，以防止数据丢失。可以使用`tar`命令创建压缩备份。 ```bash tar -zcvf /home/gpadmin/master.tar.gz $MASTER_DATA_DIRECTORY ``` 5. **运行数据库...
【greenplum】greenplum 如何删除临时schema(孤立schema)
LiangHC
11-16 3156
how to clean orphan temp schemas in greenplum; drop schema if exists pg_temp_XXXX cascade; greenplum 如何删除临时schema
Greenplum分布式安装及增加节点
Du.的博客
03-25 3067
1. Greenplum简介 Greenplum是Pivotal公司基于PostgreSQL开发的一个面向数据仓库的关系型数据库，是开源的。有三个关键词可以描述： 1. Shared Nothing 各个处理单元都有自己私有的CPU/内存/硬盘等，不存在共享资源，各处理单元之间通过协议通信，并行处理和扩展能力更好。各节点相互独立，各自处理自己的数据，处理后的结果可能向上层汇总或在节点间流转。Share-Nothing架构在扩展性和成本上都具有明显优势。 2. MPP(Massively Parall
greenplum关闭某个segment host节点实验
wangning0714的博客
04-01 8972
可以看到位于hadoop108上的四个primary节点已经失败了，位于hadoop107上的mirror节点已经变为primary节点。其中Master Host 为 Hadoop106 ,Segment Host为 Hadoop107 Hadoop108。执行gpstate可以看到位于hadoop108上的四个节点已经down掉。现在down掉hadoop108 查看集群状态及执行sql查询功能。查询测试数据在segment节点分布状态。实验：关闭hadoop108节点。
Greenplum中装载和卸载数据
行者牛仔
07-21 9073
详细介绍GP中装载和卸载数据，包括概述、装载数据的方式和卸载数据的方式等。
Greenplum 添加或删除standby master节点
weixin_33910137的博客
12-21 1055
Greenplum支持master节点的standby，如果你在初始化集群时没有创建standby节点，或者原来的standby节点坏了或者其他原因，要重搭standby。 本文将告诉你怎么做。 1. 如果要新建standby，但是原来已有standby，首先要删除它。 gpinitstandby -r 如果原来的standby只是某种原因挂了，不需要删...
Greenplum Database 6（开源版） 安装升级卸载及日常维护手册
weixin_45428187的博客
08-06 1809
Greenplum Database 6（开源版） 安装升级卸载及日常维护手册
【遇到‘NoneType‘ object has no attribute ‘SetGeoTransform‘】
qq_44691564的博客
04-06 1004
666
gpstop failed. (Reason='int() argument must be a string or a number, not 'NoneType'') exiting...
wxc20062006的专栏
08-18 2974
OS Version: CentOS Linux release 7.2.1511 (Core)  greenplum version: 4.3.8 问题：在初始化过程中遇到如下错误，并且master上的postgres进行已经启动，segment上的所有进程都没有启动。 20170817:15:55:11:009635 gpstop:mdw:gpadmin-[INFO]:-
[报错]深析AttributeError: ‘NoneType‘ object has no attribute ‘xxx‘（持更）
热门推荐
panbaoran913的博客
05-08 15万+
有相关的博客还要写它的原因在于下面的博客讲了各自的重点。因此，我将深入刨析原因，以及导致该原因出现的几种问题！ 参考博文： 《AttributeError: ‘NoneType’ object has no attribute……错误分析》 《【报错分析】AttributeError: ‘NoneType’ object has no attribute ‘xxx’》 《成功解决AttributeError: ‘NoneType’ object has no attribute ‘find_all’》
【报错分析】AttributeError: 'NoneType' object has no attribute 'xxx'
ocean_R的博客
04-18 5万+
问题背景： 通过cv2.imread读取.png格式的数据时发生如下报错： AttributeError: 'NoneType' object has no attribute 'shape' 分析： 在Python中，NoneType是一个类型，如同int、float一样。如： >>> a = None >>> type(a) <class 'Non...
解决服务器重启，GreenPlum无法启动问题
MyySophia的博客
09-17 1606
一台测试服务器，由于升级glib的时候直接把系统搞死，机器无法启动，后来机器就回来之后，发现GP 启动不起来了。 gp启动时报错 home]$ gpstart -a 20210917:11:05:30:028785 gpstart:gptest01:gpadmin-[INFO]:-Starting gpstart with args: -a 20210917:11:05:30:028785 gpstart:gptest01:gpadmin-[INFO]:-Gathering information
Greenplum 删除账号语法
最新发布
08-29
<think> 我们之前讨论的是Greenplum的访问控制，现在用户询问删除账号的语法。注意，Greenplum基于PostgreSQL，因此删除用户（账号）的语法与PostgreSQL类似。 在Greenplum中，删除用户（账号）使用`DROP ROLE`或`DROP USER`命令，因为Greenplum中USER和ROLE是等价的（USER是ROLE的别名，具有登录权限）。 语法： DROP ROLE [IF EXISTS] username [, ...]; 或者 DROP USER [IF EXISTS] username [, ...]; 注意： 1. 需要具有相应的权限（通常需要是超级用户或角色所有者）。 2. 在删除角色之前，必须确保该角色没有拥有任何数据库对象（如表、视图等），否则需要先转移所有权或删除这些对象。 3. 如果角色被授予了其他角色的权限，也需要先撤销这些权限（或者使用CASCADE选项自动解除依赖）。 可选参数： - `IF EXISTS`：如果指定，当角色不存在时不会报错，仅发出一个提示。 - `CASCADE`：自动删除依赖于该角色的对象（比如该角色拥有的所有对象）以及该角色在其他角色中的成员关系。注意：使用CASCADE要非常小心，因为它会连带删除很多对象。 示例： 1. 删除一个用户（角色）`test_user`，如果存在则删除，且级联删除其拥有的对象： ```sql DROP ROLE IF EXISTS test_user CASCADE; ``` 2. 同时删除多个用户： ```sql DROP ROLE user1, user2; ``` 注意事项： - Greenplum是一个分布式系统，这个操作会在所有Segment上同步执行。 - 不能删除当前会话中正在使用的角色。 - 超级用户（如gpadmin）不能被删除，除非以另一个超级用户身份登录进行删除（但通常建议不要删除超级用户）。 操作步骤建议： 1. 检查该角色拥有的对象： ```sql SELECT * FROM pg_roles WHERE rolname = 'test_user'; -- 查看角色是否存在 REASSIGN OWNED BY test_user TO new_owner; -- 转移所有权（如果不想删除对象） DROP OWNED BY test_user; -- 删除该角色拥有的所有对象 ``` 2. 然后再删除角色： ```sql DROP ROLE test_user; ``` 安全提示： - 删除账号是一个敏感操作，请确保操作前有备份。 - 在生成环境中，建议先在测试环境中验证。 引用：Greenplum官方文档关于DROP ROLE的部分[^1]。 相关问题： 1. 如何在Greenplum中创建新用户？ 2. 如何修改Greenplum用户的密码？ 3. 如何查看Greenplum中现有的用户？ 4. 如何处理Greenplum用户的对象依赖？ 5. Greenplum中的用户权限管理策略是什么？ 现在，我们按照用户的要求，给出删除账号的语法说明。 </think> ### 📝 Greenplum 数据库删除账号语法详解 在 Greenplum 中删除账号（用户）使用 **`DROP ROLE`** 或 **`DROP USER`** 命令（两者等价），完整语法如下： ```sql -- 基本语法 DROP ROLE [IF EXISTS] username; -- 或 DROP USER [IF EXISTS] username; -- 完整语法 DROP ROLE [IF EXISTS] username [, ...] [CASCADE | RESTRICT]; ``` #### ✨ 参数说明： | **参数** | **作用** | **示例** | |---------------|-------------------------------------------------------------------------|-----------------------------------| | `IF EXISTS` | 当用户不存在时不报错 | `DROP ROLE IF EXISTS test_user;` | | `username` | 要删除的用户名（可同时删除多个用户） | `DROP USER user1, user2;` | | `CASCADE` | **级联删除**用户拥有的所有对象（表/视图/函数等） | `DROP ROLE dev_user CASCADE;` | | `RESTRICT` | **禁止删除**如果用户拥有对象（默认行为） | `DROP ROLE dev_user RESTRICT;` | #### ️ 重要注意事项： 1. **权限要求** 需是超级用户（如 `gpadmin`）或有 `CREATEROLE` 权限的用户执行 2. **依赖处理** - 若用户拥有数据库对象，必须使用 `CASCADE` 或提前转移所有权： ```sql REASSIGN OWNED BY old_user TO new_user; -- 转移所有权 DROP OWNED BY old_user; -- 删除用户的对象 ``` 3. **系统用户保护** 无法删除内置角色（如 `gpadmin`）或当前会话用户 4. **分布式特性** 操作会自动同步到所有 Segment 节点，无需单独操作 #### 💡 操作示例： ```sql -- 安全删除用户（检查依赖） DROP ROLE IF EXISTS temp_user RESTRICT; -- 强制删除用户及其所有对象 DROP USER legacy_user CASCADE; -- 批量删除多个用户 DROP ROLE user_2020, user_2021 CASCADE; ``` #### 🔒 最佳实践： 1. 删除前备份用户权限： ```sql SELECT * FROM pg_roles WHERE rolname = 'target_user'; ``` 2. 生产环境建议先禁用账号： ```sql ALTER ROLE target_user NOLOGIN; -- 禁止登录 ``` 3. 操作后验证删除： ```sql SELECT rolname FROM pg_roles WHERE rolname = 'deleted_user'; ``` > 📌 官方提示：在 Greenplum 7+ 中，`DROP USER` 是 `DROP ROLE` 的别名，两者功能完全一致[^1]。 --- ### 📎 相关问题 1. 如何查看 Greenplum 中所有用户的权限分配？ 2. Greenplum 中如何修改用户密码和安全策略？ 3. 删除用户时出现 _"role cannot be dropped because some objects depend on it"_ 错误该如何解决？ 4. Greenplum 与 PostgreSQL 在用户管理方面有哪些关键差异？ 5. 如何批量导出/导入 Greenplum 的用户权限配置？
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值