轉(zhuǎn)載自：li0924的博客《Greenplum failed segment的恢復(fù)方法》

【前記】

Segment檢測及故障切換機制
GP Master首先會檢測Primary狀態(tài)，如果Primary不可連通，那么將會檢測Mirror狀態(tài)，Primary/Mirror狀態(tài)總共有4種：
1. Primary活著，Mirror活著。GP Master探測Primary成功之后直接返回，進行下一個Segment檢測；
2. Primary活著，Mirror掛了。GP Master探測Primary成功之后，通過Primary返回的狀態(tài)得知Mirror掛掉了（Mirror掛掉之后，Primary將會探測到，將自己變成ChangeTracking模式），這時候更新Master元信息，進行下一個Segment檢測；
3. Primary掛了，Mirror活著。GP Master探測Primary失敗之后探測Mirror，發(fā)現(xiàn)Mirror是活著，這時候更新Master上面的元信息，同時使Mirror接管Primary（故障切換），進行下一個Segment檢測；
4. Primary掛了，Mirror掛了。GP Master探測Primary失敗之后探測Mirror，Mirror也是掛了，直到重試最大值，結(jié)束這個Segment的探測，也不更新Master元信息了，進行下一個Segment檢測。
上面的2-4需要進行g(shù)precoverseg進行segment恢復(fù)。

對失敗的segment節(jié)點；啟動時會直接跳過，忽略。

[gpadmin@mdw ~]$ gpstart 20160718:18:43:27:002949 gpstart:mdw:gpadmin-[INFO]:-Starting gpstart with args: 20160718:18:43:27:002949 gpstart:mdw:gpadmin-[INFO]:-Gathering information and validating the environment... 20160718:18:43:27:002949 gpstart:mdw:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 4.3.8.1 build 1' 20160718:18:43:28:002949 gpstart:mdw:gpadmin-[INFO]:-Greenplum Catalog Version: '201310150' 20160718:18:43:28:002949 gpstart:mdw:gpadmin-[INFO]:-Starting Master instance in admin mode 20160718:18:43:30:002949 gpstart:mdw:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information 20160718:18:43:30:002949 gpstart:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160718:18:43:30:002949 gpstart:mdw:gpadmin-[INFO]:-Setting new master era 20160718:18:43:30:002949 gpstart:mdw:gpadmin-[INFO]:-Master Started... 20160718:18:43:30:002949 gpstart:mdw:gpadmin-[INFO]:-Shutting down master 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[WARNING]:-Skipping startup of segment marked down in configuration: on sdw2 directory /home/gpadmin/gpdata/gpdatam/gpseg0 <<<<< 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:--------------------------- 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:-Master instance parameters 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:--------------------------- 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:-Database = template1 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:-Master Port = 1921 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:-Master directory = /home/gpadmin/gpdata/pgmaster/gpseg-1 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:-Timeout = 600 seconds 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:-Master standby = Off 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:--------------------------------------- 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:-Segment instances that will be started 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:--------------------------------------- 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:- Host Datadir Port Role 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:- sdw1 /home/gpadmin/gpdata/gpdatap/gpseg0 40000 Primary 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:- sdw2 /home/gpadmin/gpdata/gpdatap/gpseg1 40000 Primary 20160718:18:43:32:002949 gpstart:mdw:gpadmin-[INFO]:- sdw1 /home/gpadmin/gpdata/gpdatam/gpseg1 50000 MirrorContinue with Greenplum instance startup Yy|Nn (default=N): > y 20160718:18:43:34:002949 gpstart:mdw:gpadmin-[INFO]:-Commencing parallel primary and mirror segment instance startup, please wait... ........... 20160718:18:43:45:002949 gpstart:mdw:gpadmin-[INFO]:-Process results... 20160718:18:43:45:002949 gpstart:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160718:18:43:45:002949 gpstart:mdw:gpadmin-[INFO]:- Successful segment starts = 3 20160718:18:43:45:002949 gpstart:mdw:gpadmin-[INFO]:- Failed segment starts = 0 20160718:18:43:45:002949 gpstart:mdw:gpadmin-[WARNING]:-Skipped segment starts (segments are marked down in configuration) = 1 <<<<<<<< 20160718:18:43:45:002949 gpstart:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160718:18:43:45:002949 gpstart:mdw:gpadmin-[INFO]:- 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[INFO]:-Successfully started 3 of 3 segment instances, skipped 1 other segments 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[WARNING]:-**************************************************************************** 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[WARNING]:-There are 1 segment(s) marked down in the database 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[WARNING]:-To recover from this current state, review usage of the gprecoverseg 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[WARNING]:-management utility which will recover failed segment instance databases. 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[WARNING]:-**************************************************************************** 20160718:18:43:46:002949 gpstart:mdw:gpadmin-[INFO]:-Starting Master instance mdw directory /home/gpadmin/gpdata/pgmaster/gpseg-1 20160718:18:43:48:002949 gpstart:mdw:gpadmin-[INFO]:-Command pg_ctl reports Master mdw instance active 20160718:18:43:49:002949 gpstart:mdw:gpadmin-[INFO]:-No standby master configured. skipping... 20160718:18:43:49:002949 gpstart:mdw:gpadmin-[WARNING]:-Number of segments not attempted to start: 1 20160718:18:43:49:002949 gpstart:mdw:gpadmin-[INFO]:-Check status of database with gpstate utility

查看數(shù)據(jù)庫的mirror的節(jié)點啟動狀態(tài)

[gpadmin@mdw ~]$ gpstate -m 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:-Starting gpstate with args: -m 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.8.1 build 1' 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.8.1 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Apr 20 2016 08:08:56' 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:-------------------------------------------------------------- 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:--Current GPDB mirror list and status 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:--Type = Spread 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:-------------------------------------------------------------- 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:- Mirror Datadir Port Status Data Status 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[WARNING]:-sdw2 /home/gpadmin/gpdata/gpdatam/gpseg0 50000 Failed <<<<<<<< 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:- sdw1 /home/gpadmin/gpdata/gpdatam/gpseg1 50000 Passive Synchronized 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[INFO]:-------------------------------------------------------------- 20160718:18:45:48:003084 gpstate:mdw:gpadmin-[WARNING]:-1 segment(s) configured as mirror(s) have failed

可直觀看出“[WARNING]:-sdw2 /home/gpadmin/gpdata/gpdatam/gpseg0 50000 Failed ”

如何恢復(fù)這個mirror segment呢？當(dāng)然primary segment也是這樣恢復(fù)的

首先產(chǎn)生一個恢復(fù)的配置文件 ： gprecoverseg -o ./recov

[gpadmin@mdw ~]$ gprecoverseg -o ./recov 20160718:18:47:04:003134 gprecoverseg:mdw:gpadmin-[INFO]:-Starting gprecoverseg with args: -o ./recov 20160718:18:47:04:003134 gprecoverseg:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.8.1 build 1' 20160718:18:47:04:003134 gprecoverseg:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.8.1 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Apr 20 2016 08:08:56' 20160718:18:47:04:003134 gprecoverseg:mdw:gpadmin-[INFO]:-Checking if segments are ready 20160718:18:47:04:003134 gprecoverseg:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160718:18:47:06:003134 gprecoverseg:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160718:18:47:07:003134 gprecoverseg:mdw:gpadmin-[INFO]:-Configuration file output to ./recov successfully.

查看恢復(fù)的配置文件；可以知道哪些segment需要恢復(fù)

[gpadmin@mdw ~]$ cat recov filespaceOrder=fastdisk sdw2:50000:/home/gpadmin/gpdata/gpdatam/gpseg0

使用這個配置文件進行恢復(fù) ： gprecoverseg -i ./recov

[gpadmin@mdw ~]$ gprecoverseg -i ./recov 20160718:18:47:33:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Starting gprecoverseg with args: -i ./recov 20160718:18:47:34:003187 gprecoverseg:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.8.1 build 1' 20160718:18:47:34:003187 gprecoverseg:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.8.1 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Apr 20 2016 08:08:56' 20160718:18:47:34:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Checking if segments are ready 20160718:18:47:34:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Greenplum instance recovery parameters 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:---------------------------------------------------------- 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Recovery from configuration -i option supplied 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:---------------------------------------------------------- 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Recovery 1 of 1 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:---------------------------------------------------------- 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Synchronization mode = Incremental 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Failed instance host = sdw2 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Failed instance address = sdw2 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Failed instance directory = /home/gpadmin/gpdata/gpdatam/gpseg0 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Failed instance port = 50000 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Failed instance replication port = 51000 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Failed instance fastdisk directory = /data/gpdata/seg1/pg_mir_cdr/gpseg0 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Recovery Source instance host = sdw1 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Recovery Source instance address = sdw1 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Recovery Source instance directory = /home/gpadmin/gpdata/gpdatap/gpseg0 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Recovery Source instance port = 40000 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Recovery Source instance replication port = 41000 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Recovery Source instance fastdisk directory = /data/gpdata/seg1/pg_pri_cdr/gpseg0 20160718:18:47:35:003187 gprecoverseg:mdw:gpadmin-[INFO]:- Recovery Target = in-place 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Process results... 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Done updating primaries 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:-****************************************************************** 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Updating segments for resynchronization is completed. 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:-For segments updated successfully, resynchronization will continue in the background. 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:- 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:-Use gpstate -s to check the resynchronization progress. 20160718:18:48:06:003187 gprecoverseg:mdw:gpadmin-[INFO]:-******************************************************************

查看恢復(fù)狀態(tài)

[gpadmin@mdw ~]$ gpstate -m 20160718:18:48:39:003353 gpstate:mdw:gpadmin-[INFO]:-Starting gpstate with args: -m 20160718:18:48:39:003353 gpstate:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.8.1 build 1' 20160718:18:48:39:003353 gpstate:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.8.1 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Apr 20 2016 08:08:56' 20160718:18:48:39:003353 gpstate:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:-------------------------------------------------------------- 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:--Current GPDB mirror list and status 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:--Type = Spread 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:-------------------------------------------------------------- 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:- Mirror Datadir Port Status Data Status 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:- sdw2 /home/gpadmin/gpdata/gpdatam/gpseg0 50000 Passive Resynchronizing 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:- sdw1 /home/gpadmin/gpdata/gpdatam/gpseg1 50000 Passive Synchronized 20160718:18:48:40:003353 gpstate:mdw:gpadmin-[INFO]:--------------------------------------------------------------

到上一步，數(shù)據(jù)庫的主備就恢復(fù)了，但是還有一步，是可選的。
你要不要把primary , mirror角色對調(diào)一下，因為現(xiàn)在mirror和primary和優(yōu)先角色是相反的。
如果要對調(diào)，使用以下命令，會停庫來處理。

gprecoverseg -r

用于修復(fù)Segment的是gprecoverseg。使用方式比較簡單，有限的幾個主要參數(shù)如下：
-i ：主要參數(shù)，用于指定一個配置文件，該配置文件描述了需要修復(fù)的Segment和修復(fù)后的目的位置。
-F ：可選項，指定后，gprecoverseg會將”-i”中指定的或標(biāo)記”d”的實例刪除，并從活著的Mirror復(fù)制一個完整一份到目標(biāo)位置。
-r ：當(dāng)FTS發(fā)現(xiàn)有Primary宕機并進行主備切換，在gprecoverseg修復(fù)后，擔(dān)當(dāng)Primary的Mirror角色并不會立即切換回來，就會導(dǎo)致部分主機上活躍的Segment過多從而引起性能瓶頸。因此需要恢復(fù)Segment原先的角色，稱為re-balance。

總結(jié)

以上是生活随笔為你收集整理的Greenplum failed segment的恢复方法的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。