greenplum如何恢复故障segment

最新推荐文章于 2024-07-24 10:20:36 发布
最新推荐文章于 2024-07-24 10:20:36 发布
阅读量3.4k 收藏 1
点赞数
分类专栏： greenplum
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/dream19881003/article/details/89186818
版权
本文档记录了在Greenplum环境中，如何处理故障segment并切换镜像角色。通过`gpstart`命令启动并检查GPDB状态，发现多个mirror segment充当了primary角色。使用`gpstate`命令确认了这一问题，接着通过`gprecoverseg -r`命令进行恢复。在执行恢复操作时，需确保故障segment不被启动，以保证数据一致性。最终，所有segment恢复正常运行。
摘要由CSDN通过智能技术生成

环境如下：

more /etc/redhat-release
Red Hat Enterprise Linux Server release 7.5 (Maipo)
系统安装采取最小化安装。

greenplum-db-5.16.0-rhel7-x86_64.zip

more /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

greenplum如何恢复故障segment及如何切换mirror和primary

--启动gp
[gpadmin@rhmdw ~]$  gpssh -f /gp/app/config/hostlist -e 'netstat -nltp | grep postgres'
[  rhmdw] netstat -nltp | grep postgres
[  rhmdw] (Not all processes could be identified, non-owned process info
[  rhmdw]  will not be shown, you would have to be root to see it all.)
[rhsdw03] netstat -nltp | grep postgres
[rhsdw03] (Not all processes could be identified, non-owned process info
[rhsdw03]  will not be shown, you would have to be root to see it all.)
[ rhsdw2] netstat -nltp | grep postgres
[ rhsdw2] (No info could be read for "-p": geteuid()=1000 but you should be root.)
[rhsdw04] netstat -nltp | grep postgres
[rhsdw04] (Not all processes could be identified, non-owned process info
[rhsdw04]  will not be shown, you would have to be root to see it all.)
[ rhsdw1] netstat -nltp | grep postgres
[ rhsdw1] (No info could be read for "-p": geteuid()=1000 but you should be root.)
[gpadmin@rhmdw ~]$ gpstart -a
20190404:13:44:18:002757 gpstart:rhmdw:gpadmin-[INFO]:-Starting gpstart with args: -a
20190404:13:44:18:002757 gpstart:rhmdw:gpadmin-[INFO]:-Gathering information and validating the environment...
20190404:13:44:18:002757 gpstart:rhmdw:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 5.16.0 build commit:23cec7df0406d69d6552a4bbb77035dba4d7dd44'
20190404:13:44:18:002757 gpstart:rhmdw:gpadmin-[INFO]:-Greenplum Catalog Version: '301705051'
20190404:13:44:18:002757 gpstart:rhmdw:gpadmin-[INFO]:-Starting Master instance in admin mode
20190404:13:44:19:002757 gpstart:rhmdw:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20190404:13:44:19:002757 gpstart:rhmdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20190404:13:44:19:002757 gpstart:rhmdw:gpadmin-[INFO]:-Setting new master era
20190404:13:44:19:002757 gpstart:rhmdw:gpadmin-[INFO]:-Master Started...
20190404:13:44:19:002757 gpstart:rhmdw:gpadmin-[INFO]:-Shutting down master
20190404:13:44:20:002757 gpstart:rhmdw:gpadmin-[INFO]:-Commencing parallel primary and mirror segment instance startup, please wait...
...
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-Process results...
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-   Successful segment starts                                            = 5   <<===============启动成功5个seg
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-   Failed segment starts                                                = 0
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-   Skipped segment starts (segments are marked down in configuration)   = 0
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-Successfully started 5 of 5 segment instances
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:44:23:002757 gpstart:rhmdw:gpadmin-[INFO]:-Starting Master instance rhmdw directory /gp/gpdata/master/gpseg-1
20190404:13:44:25:002757 gpstart:rhmdw:gpadmin-[INFO]:-Command pg_ctl reports Master rhmdw instance active
20190404:13:44:25:002757 gpstart:rhmdw:gpadmin-[INFO]:-No standby master configured.  skipping...
20190404:13:44:25:002757 gpstart:rhmdw:gpadmin-[INFO]:-Database successfully started
[gpadmin@rhmdw ~]$

--查看状态：
[gpadmin@rhmdw ~]$ gpstate -m
20190404:13:45:20:002985 gpstate:rhmdw:gpadmin-[INFO]:-Starting gpstate with args: -m
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 5.16.0 build commit:23cec7df0406d69d6552a4bbb77035dba4d7dd44'
20190404:13:45:21:002985 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'
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:--------------------------------------------------------------
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:--Current GPDB mirror list and status
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:--Type = Spread
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:--------------------------------------------------------------
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:-   Mirror    Datadir                    Port   Status              Data Status       
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw2    /gp/gpdata/mirror/gpseg0   7000   Acting as Primary   Change Tracking
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw1    /gp/gpdata/mirror/gpseg1   7000   Acting as Primary   Change Tracking
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw04   /gp/gpdata/mirror/gpseg2   7000   Passive             Synchronized
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:-   rhsdw03   /gp/gpdata/mirror/gpseg3   7000   Acting as Primary   Change Tracking
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[INFO]:--------------------------------------------------------------
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[WARNING]:-3 segment(s) configured as mirror(s) are acting as primaries
20190404:13:45:21:002985 gpstate:rhmdw:gpadmin-[WARNING]:-3 mirror segment(s) acting as primaries are in change tracking

查看状态：
rhsdw2、rhsdw1、rhsdw03主机mirror 充当primary启动，检查端口，发现故障节点6000端口未启动
[gpadmin@rhmdw ~]$  gpssh -f /gp/app/config/hostlist -e 'netstat -nltp | grep postgres'
[ rhsdw2] netstat -nltp | grep postgres
[ rhsdw2] (Not all processes could be identified, non-owned process info
[ rhsdw2]  will not be shown, you would have to be root to see it all.)
[ rhsdw2] tcp        0      0 0.0.0.0:7000            0.0.0.0:*               LISTEN      13492/postgres      
[ rhsdw2] tcp6       0      0 :::7000                 :::*                    LISTEN      13492/postgres      
[  rhmdw] netstat -nltp | grep postgres
[  rhmdw] (Not all processes could be identified, non-owned process info
[  rhmdw]  will not be shown, you would have to be root to see it all.)
[  rhmdw] tcp        0      0 0.0.0.0:5432            0.0.0.0:*               LISTEN      2833/postgres       
[  rhmdw] tcp6       0      0 :::55763                :::*                    LISTEN      2840/postgres:  543
[  rhmdw] tcp6       0      0 :::5432                 :::*                    LISTEN      2833/postgres       
[rhsdw03] netstat -nltp | grep postgres
[rhsdw03] (Not all processes could be identified, non-owned process info
[rhsdw03]  will not be shown, you would have to be root to see it all.)
[rhsdw03] tcp        0      0 192.168.15.205:9000     0.0.0.0:*               LISTEN      25726/postgres:  60
[rhsdw03] tcp        0      0 0.0.0.0:6000            0.0.0.0:*               LISTEN      25714/postgres      
[rhsdw03] tcp        0      0 0.0.0.0:7000            0.0.0.0:*               LISTEN      25713/postgres      
[rhsdw03] tcp6       0      0 :::6000                 :::*                    LISTEN      25714/postgres      
[rhsdw03] tcp6       0      0 :::7000                 :::*                    LISTEN      25713/postgres      
[ rhsdw1] netstat -nltp | grep postgres
[ rhsdw1] (Not all processes could be identified, non-owned process info
[ rhsdw1]  will not be shown, you would have to be root to see it all.)
[ rhsdw1] tcp        0      0 0.0.0.0:7000            0.0.0.0:*               LISTEN      19957/postgres      
[ rhsdw1] tcp6       0      0 :::7000                 :::*                    LISTEN      19957/postgres      
[rhsdw04] netstat -nltp | grep postgres
[rhsdw04] (Not all processes could be identified, non-owned process info
[rhsdw04]  will not be shown, you would have to be root to see it all.)
[rhsdw04] tcp        0      0 192.168.15.206:8000     0.0.0.0:*               LISTEN      13713/postgres:  70
[rhsdw04] tcp        0      0 0.0.0.0:7000            0.0.0.0:*               LISTEN      13707/postgres      
[rhsdw04] tcp6       0      0 :::7000                 :::*                    LISTEN      13707/postgres
通过gpstate -b查看，发现三个seg端postmaster.pid文件丢失
[gpadmin@rhmdw ~]$ gpstate -b
20190404:13:45:35:003051 gpstate:rhmdw:gpadmin-[INFO]:-Starting gpstate with args: -b
20190404:13:45:36:003051 gpstate:rhmdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 5.16.0 build commit:23cec7df0406d69d6552a4bbb77035dba4d7dd44'
20190404:13:45:36:003051 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'
20190404:13:45:36:003051 gpstate:rhmdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20190404:13:45:36:003051 gpstate:rhmdw:gpadmin-[INFO]:-Gathering data from segments...
..
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-Greenplum instance status summary
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Master instance                                           = Active
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Master standby                                            = No master standby configured
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total segment instance count from metadata                = 8
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Primary Segment Status
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total primary segments                                    = 4
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total primary segment valid (at master)                   = 1
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[WARNING]:-Total primary segment failures (at master)                = 3                              <<<<<<<<
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[WARNING]:-Total number of postmaster.pid files missing              = 3                              <<<<<<<<
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid files found                = 1
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[WARNING]:-Total number of postmaster.pid PIDs missing               = 3                              <<<<<<<<
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs found                 = 1
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[WARNING]:-Total number of /tmp lock files missing                   = 3                              <<<<<<<<
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of /tmp lock files found                     = 1
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[WARNING]:-Total number postmaster processes missing                 = 3                              <<<<<<<<
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number postmaster processes found                   = 1
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Mirror Segment Status
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total mirror segments                                     = 4
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total mirror segment valid (at master)                    = 4
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total mirror segment failures (at master)                 = 0
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid files missing              = 0
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid files found                = 4
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs missing               = 0
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs found                 = 4
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of /tmp lock files missing                   = 0
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of /tmp lock files found                     = 4
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number postmaster processes missing                 = 0
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number postmaster processes found                   = 4
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[WARNING]:-Total number mirror segments acting as primary segments   = 3                              <<<<<<<<
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-   Total number mirror segments acting as mirror segments    = 1
20190404:13:45:38:003051 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------

检查正常节点启动进程，发现是postgres启动，尝试在故障seg端启动
[root@rhsdw03 ~]# ps -ef |grep postgre
gpadmin  25713     1  0 13:43 ?        00:00:00 /gp/app/bin/postgres -D /gp/gpdata/mirror/gpseg3 -p 7000 --gp_dbid=8 --gp_num_contents_in_cluster=4 --silent-mode=true -i -M quiescent --gp_contentid=3
gpadmin  25714     1  0 13:43 ?        00:00:00 /gp/app/bin/postgres -D /gp/gpdata/primary/gpseg2 -p 6000 --gp_dbid=6 --gp_num_contents_in_cluster=4 --silent-mode=true -i -M quiescent --gp_contentid=2
gpadmin  25715 25713  0 13:43 ?        00:00:00 postgres:  7000, logger process   
gpadmin  25716 25714  0 13:43 ?        00:00:00 postgres:  6000, logger process   
gpadmin  25723 25713  0 13:43 ?        00:00:00 postgres:  7000, primary process   
gpadmin  25724 25714  0 13:43 ?        00:00:00 postgres:  6000, primary process   
gpadmin  25725 25723  0 13:43 ?        00:00:00 postgres:  7000, primary recovery process   
gpadmin  25726 25724  0 13:43 ?        00:00:00 postgres:  6000, primary receiver ack process   
gpadmin  25727 25724  0 13:43 ?        00:00:00 postgres:  6000, primary sender process   
gpadmin  25728 25724  0 13:43 ?        00:00:00 postgres:  6000, primary consumer ack process   
gpadmin  25729 25724  0 13:43 ?        00:00:00 postgres:  6000, primary recovery process   
gpadmin  25732 25713  0 13:43 ?        00:00:00 postgres:  7000, stats collector process   
gpadmin  25733 25713  0 13:43 ?        00:00:00 postgres:  7000, writer process   
gpadmin  25734 25713  0 13:43 ?        00:00:00 postgres:  7000, checkpointer process   
gpadmin  25735 25713  0 13:43 ?        00:00:00 postgres:  7000, sweeper process   
gpadmin  25736 25713  0 13:43 ?        00:00:00 postgres:  7000, stats sender process   
gpadmin  25737 25713  0 13:43 ?        00:00:00 postgres:  7000, wal writer process   
gpadmin  25740 25714  0 13:43 ?        00:00:00 postgres:  6000, stats collector process   
gpadmin  25741 25714  0 13:43 ?        00:00:00 postgres:  6000, writer process   
gpadmin  25742 25714  0 13:43 ?        00:00:00 postgres:  6000, checkpointer process   
gpadmin  25743 25714  0 13:43 ?        00:00:00 postgres:  6000, sweeper process   
gpadmin  25744 25714  0 13:43 ?        00:00:00 postgres:  6000, stats sender process   
gpadmin  25745 25714  0 13:43 ?        00:00:00 postgres:  6000, wal writer process   
root     26091 24220  0 13:51 pts/8    00:00:00 grep --color=auto postgre

启动参数内容
[gpadmin@rhsdw03 gpseg2]$ more /gp/gpdata/primary/gpseg2/postmaster.opts
/gp/app/bin/postgres "-D" "/gp/gpdata/primary/gpseg2" "-p" "6000" "--gp_dbid=6" "--gp_num_contents_in_cluster=4" "--silent-mode=true" "-i" "-M" "quiescent" "--gp_contentid=2"

启动故障节点：
[gpadmin@rhsdw04 gpseg3]$ /gp/app/bin/postgres "-D" "/gp/gpdata/primary/gpseg3" "-p" "6000" "--gp_dbid=7" "--gp_num_contents_in_cluster=4" "--silent-mode=true" "-i" "-M" "quiescent" "--gp_contentid=3"
[gpadmin@rhsdw04 gpseg3]$ ps -ef | grep postgres
gpadmin  13707     1  0 13:42 ?        00:00:00 /gp/app/bin/postgres -D /gp/gpdata/mirror/gpseg2 -p 7000 --gp_dbid=9 --gp_num_contents_in_cluster=4 --silent-mode=true -i -M quiescent --gp_contentid=2
gpadmin  13708 13707  0 13:42 ?        00:00:00 postgres:  7000, logger process   
gpadmin  13712 13707  0 13:42 ?        00:00:00 postgres:  7000, mirror process   
gpadmin  13713 13712  0 13:42 ?        00:00:00 postgres:  7000, mirror receiver process   
gpadmin  13714 13712  0 13:42 ?        00:00:00 postgres:  7000, mirror consumer process   
gpadmin  13715 13712  0 13:42 ?        00:00:00 postgres:  7000, mirror consumer writer process   
gpadmin  13716 13712  0 13:42 ?        00:00:00 postgres:  7000, mirror consumer append only process   
gpadmin  13717 13712  0 13:42 ?        00:00:00 postgres:  7000, mirror sender ack process   
gpadmin  13867     1  1 13:56 ?        00:00:00 /gp/app/bin/postgres -D /gp/gpdata/primary/gpseg3 -p 6000 --gp_dbid=7 --gp_num_contents_in_cluster=4 --silent-mode=true -i -M quiescent --gp_contentid=3
gpadmin  13868 13867  0 13:56 ?        00:00:00 postgres:  6000, logger process   
gpadmin  13870 12742  0 13:56 pts/7    00:00:00 grep --color=auto postgres

分别启动另外两个故障seg
[gpadmin@rhsdw1 pg_log]$ /gp/app/bin/postgres "-D" "/gp/gpdata/primary/gpseg0" "-p" "6000" "--gp_dbid=2" "--gp_num_contents_in_cluster=4" "--silent-mode=true" "-i" "-M" "quiescent" "--gp_contentid=0"
[gpadmin@rhsdw2 ~]$ /gp/app/bin/postgres "-D" "/gp/gpdata/primary/gpseg1" "-p" "6000" "--gp_dbid=3" "--gp_num_contents_in_cluster=4" "--silent-mode=true" "-i" "-M" "quiescent" "--gp_contentid=1"

管理节点查看状态：
[gpadmin@rhmdw ~]$ gpstate -b
20190404:14:01:08:005024 gpstate:rhmdw:gpadmin-[INFO]:-Starting gpstate with args: -b
20190404:14:01:08:005024 gpstate:rhmdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 5.16.0 build commit:23cec7df0406d69d6552a4bbb77035dba4d7dd44'
20190404:14:01:08:005024 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'
20190404:14:01:08:005024 gpstate:rhmdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20190404:14:01:08:005024 gpstate:rhmdw:gpadmin-[INFO]:-Gathering data from segments...
..
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-Greenplum instance status summary
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Master instance                                           = Active
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Master standby                                            = No master standby configured
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total segment instance count from metadata                = 8
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Primary Segment Status
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total primary segments                                    = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total primary segment valid (at master)                   = 1
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[WARNING]:-Total primary segment failures (at master)                = 3                              <<<<<<<<
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid files missing              = 0
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid files found                = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs missing               = 0
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs found                 = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of /tmp lock files missing                   = 0
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of /tmp lock files found                     = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number postmaster processes missing                 = 0
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number postmaster processes found                   = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Mirror Segment Status
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-----------------------------------------------------
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total mirror segments                                     = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total mirror segment valid (at master)                    = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total mirror segment failures (at master)                 = 0
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid files missing              = 0
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid files found                = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs missing               = 0
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs found                 = 4
20190404:14:01:10:005024 gpstate:rhmdw:gpadmin-[INFO]:-   Total number of /tmp lock files missing                  

最低0.47元/天 解锁文章
Gavin404
关注
专栏目录
Greenplum segment节点异常恢复
无锋剑
08-30 2549
Segment检测及故障切换机制 GP Master首先会检测Primary状态，如果Primary不可连通，那么将会检测Mirror状态，Primary/Mirror状态总共有4种： Primary活着，Mirror活着。GP Master探测Primary成功之后直接返回，进行下一个Segment检测； Primary活着，Mirror挂了。GP Master探测Primary成功之后，通...
Greenplum数据库中segment的故障检测与恢复
jmx_bigdata的博客
11-28 5430
1.Greenplum数据库中segment故障检测 1.1概述 Greenplum数据库服务器（Postgres）有一个子进程，该子进程为ftsprobe，主要作用是处理故障检测。 ftsprobe 监视Greenplum数据库阵列，它以可以配置的间隔连接并扫描所有segment和数据库进程。 如果 ftsprobe无法连接到segment，它会在Greenplum数据库系统目录中将seg...
【greemplum 故障恢复】10分钟掌握GreenPlum6.16.3 故障以及恢复方法
赖德发的博客
02-09 697
调整Primary和Mirror,上面的情况中有Primary和Mirror兑换的情况，所以需要把他们换回来，可以用下面的命令。©著作权归作者所有：来自51CTO博客作者李石岩的原创作品，请联系作者获取转载授权，否则将追究法律责任。等待所有的节点都是Synchronized后，segment就恢复好了。查看异常节点状态，查看数据库的mirror的节点启动状态。查看恢复的配置文件,可以知道哪些segment需要恢复。如何恢复出故障的segment状态。下面我们使用配置文件进行恢复。
Not all processes could be identified, non-owned process info will not be show解决办法
灵感点滴的分享
06-15 5135
Not all processes could be identified, non-owned process info will not be show解决办法 背景 今天在调试脚本的时候，打印出的日志中出现了 “Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.” 错误 原因 经过排查后发现脚本中有运行 nets
2020-09-19：TCP状态有哪些？
福大大架构师每日一题
09-19 5117
福哥答案2020-09-19：#福大大架构师每日一题# 答案来自此链接 11种状态 1.CLOSED状态：初始状态，表示TCP连接是“关闭的”或者“未打开的”。 2.LISTEN状态：表示服务端的某个端口正处于监听状态，正在等待客户端连接的到来。 3.SYN_SENT状态：当客户端发送SYN请求建立连接之后，客户端处于SYN_SENT状态，等待服务器发送SYN+ACK。 4.SYN_RCVD状态：当服务器收到来自客户端的连接请求SYN之后，服务器处于SYN_RCVD状态，在接收到SYN请求之后会向客户端回复
greenplum生产集群中segment故障恢复
jmx_bigdata的博客
12-15 1664
目录   一、greenplum集群环境 二、segment故障检查 2.1gpstate -m日志信息 2.2gpstate -c 日志信息 2.3gpstate -e 日志信息 2.4gpstate -s 日志信息 2.5故障说明 三、segment故障恢复 3.1在master主机上运行下面命令，重新激活失败的segment 3.2运行gpstate 命令用于验证重新同...
greenplum如何删除segment节点
DreamDB的专栏
04-20 2930
环境信息： 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集群Master與Segment节点故障检测与恢复
Greenplum中文社区
06-09 2152
了解更多G...
zabbix技术遇到的问题7--Not all processes could be identified, non-owned process info will not be shown...
weixin_44736359的博客
07-09 740
遇到的问题 [root@m01 ~]# zabbix_get -s 10.0.0.61 -k mysql.discovery (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) {"data":[]} 原因： zabbix用户不能使用netstat的-p参数 解决方法： 给netstat命令添加s权限 [roo
Linux查看进程id，以及根据进程id查看占用的端口，根据端口号查看占用的进程
lizhengyu891231的博客
09-22 2008
转载自：https://blog.csdn.net/yzpbright/article/details/81981755 1. 先根据进程名查看进程id ps aux | grep 进程名(或者ps -ef | grep 进程名) y@ubuntu:~$ ps aux | grep bitcoind y 2708 101 12.1 1611172 488580 ? ...
linux中查询端口占用情况
OceanSky的专栏
12-26 2184
Netstat 是一款命令行工具，可用于列出系统上所有的网络套接字连接情况，包括 tcp, udp 以及 unix 套接字，另外它还能列出处于监听状态（即等待接入请求）的套接字。如果你想确认系统上的 Web 服务有没有起来，你可以查看80端口有没有打开。以上功能使 netstat 成为网管和系统管理员的必备利器。   一、netstat -anp |grep 9074   [webuse...
【GreenPlum节点异常分析】
最新发布
Xc531的博客
07-24 330
查看 segment_2 对应的目录日志，发现在报连接数不足后，一个数据库自身的数据同步的 copy 操作因为无法开启事务而发生异常，导致该节点宕机。结论：节点宕机的原因是子节点连接数过多，导致数据库主从同步事务(COPY)无法正常建立连接，最终子节点宕机。2、查看上述记录的primary节点日志，发现该时期也在报连接数不够的异常。1、排查主节点相关日志，发现8:17分左右，日志报错连接数不够。，进行节点数据重平衡，节点成功恢复正常，耗时10min。，表示节点实例正在同步数据中。，显示镜像实例同步状态。
Greenplum数据库故障排查及修复
DraGon_HooRay的博客
11-25 2786
gp服务正常，存在部分segment实例丢失 gp启动失败，segment实例可用数已不足一半 gprecoverseg gprecoverseg -F gprecoverseg - 已知可能造成segment丢失的原因：频繁的内存溢出。 可能存在的问题：数据目录存在目录或文件权限不足、损坏文件等。 gpstart -v 查看启动日志明细
Linux使用netstat查看网络状态
萌兔兔MMQ！！
08-08 3870
只显示所有监听tcp端口。前2个是0:0:0:0:0:0:0:0的缩写。0.0.0.0:80 表示监听本地服务器上所有ip的80端口（0.0.0.0表示所有ip）127.0.0.1:123 表示监听本机的loopback（回环地址）地址的123端口。:::9010 表示监听本地服务器上所有ip的9010端口。形如::1:9011，表示监听IPv6的回环地址的9011端口。与本地服务器通信的另外的地址，显示规则和上面本地地址的相同。对方还没收到数据，或者还没ack的数据，还在本地缓冲区中。...
install greenplum database system
09-09 324
1．Introduction to Greenplum gp通过把任务分配给务个服务器或主机，来应对存储及处理大数据量操作的需求。 一个GP逻辑数据库就是一组独立的postgresql数据库，都同时工作以表现出一个独立...
psql: FATAL: the database system is in recovery mode - 问题定位方法与解决
热门推荐
专注数据库、大数据领域干货分享，用严谨的数据技术广交天下朋友。
03-29 1万+
首先介绍一下背景，在测试Deepgreen（Greenplum升级版）数据库时，pgbench并发数设置过多，导致数据库卡死了，在进行连接、重启、关闭时，都报同样的错误：psql: FATAL:  the database system is in recovery mode。于是尝试进行如下操作，解决了该问题，总体步骤：1.尝试登陆数据库，报错；2.查看Master上的postgres进程，发现...
greenplum 节点故障修复文档
weixin_33724570的博客
04-26 2254
greenplum集群说明 greenplum整个集群是由多台服务器组合而成，任何一台服务都有可能发生软件或硬件故障，我们一起来模拟一下任何一个节点或服务器故障后，greenplumn的容错及恢复方法 master 服务器：l-test5 standby 服务器：l-test6 segment 服务器:（primary + mirror）:l-tes...
greenplum全量恢复gprecoverseg -F出现Unable to connect to database时的相关分析及解决方法
aabc012的博客
07-28 1万+
之前有两位朋友碰到过在对greenplum的系统构架更改后，出现全量恢复gprecoverseg -F也无法正常运行的情况。 报错信息为Unable to connect to database. Retrying 1 gprecoverseg failed. (Reason='Unable to connect to database and start transaction') exiting... 有幸拷得一份虚拟机上的全部文件，对其进行分析。 发现其实出现这个问题只需要修改pg_changetra
GreenPlum分布式架构详解：性能优化与故障切换策略
在实际操作中，管理和优化GreenPlum集群涉及到监控性能指标、调整资源分配、维护数据一致性以及实施故障恢复策略。理解这些核心概念和技术细节对于有效利用GreenPlum构建企业级的数据仓库至关重要。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值