gpinitstandby

最新推荐文章于 2023-09-06 10:13:13 发布
最新推荐文章于 2023-09-06 10:13:13 发布
阅读量1.3k 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： greenplum
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/rgb_rgb/article/details/21399615
本文记录了使用gpstop、gpstart、gpstate等命令重启Greenplum数据库并检查备用主机状态的过程，随后通过gpinitstandby初始化备用主机，并再次检查备用主机的状态确认同步成功。

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

[gpadmin@mdw ~]$ gpstop -M fast
[gpadmin@mdw ~]$ gpstart 
[gpadmin@mdw ~]$ gpstate -e
20140317:17:11:47:014893 gpstate:mdw:gpadmin-[INFO]:-Starting gpstate with args: -e
20140317:17:11:47:014893 gpstate:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.2.5.0 build 1'
20140317:17:11:47:014893 gpstate:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.2.5.0 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Apr  5 2013 13:45:40'
20140317:17:11:47:014893 gpstate:mdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20140317:17:11:47:014893 gpstate:mdw:gpadmin-[INFO]:-Gathering data from segments...
... 
20140317:17:11:50:014893 gpstate:mdw:gpadmin-[INFO]:-----------------------------------------------------
20140317:17:11:50:014893 gpstate:mdw:gpadmin-[INFO]:-Segment Mirroring Status Report
20140317:17:11:50:014893 gpstate:mdw:gpadmin-[INFO]:-----------------------------------------------------
20140317:17:11:50:014893 gpstate:mdw:gpadmin-[INFO]:-All segments are running normally


[gpadmin@mdw ~]$ gpstate -f
20140317:17:11:53:015059 gpstate:mdw:gpadmin-[INFO]:-Starting gpstate with args: -f
20140317:17:11:53:015059 gpstate:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.2.5.0 build 1'
20140317:17:11:53:015059 gpstate:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.2.5.0 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Apr  5 2013 13:45:40'
20140317:17:11:53:015059 gpstate:mdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:-Standby master details
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:-----------------------
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:-   Standby address          = mdw2
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:-   Standby data directory   = /data/master/gpseg-1
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:-   Standby port             = 5432
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:-   Standby PID              = 23106
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:-   Standby status           = Standby host passive
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:--------------------------------------------------------------
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:--gp_master_mirroring table
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:--------------------------------------------------------------
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:--Summary state: Not Synchronized
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:--Detail state: Standby master too far behind
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:--Log time: 2014-03-18 07:11:30+08
20140317:17:11:54:015059 gpstate:mdw:gpadmin-[INFO]:--------------------------------------------------------------
[gpadmin@mdw ~]$ 
[gpadmin@mdw ~]$ gpinitstandby -n
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Validating environment and parameters for standby initialization...
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Checking for filespace directory /data/master/gpseg-1 on mdw2
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:------------------------------------------------------
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum standby master initialization parameters
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:------------------------------------------------------
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum master hostname               = mdw
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum master data directory         = /data/master/gpseg-1
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum master port                   = 5432
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum standby master hostname       = mdw2
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum standby master port           = 5432
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum standby master data directory = /data/master/gpseg-1
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum update system catalog         = Off
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Greenplum stop database mode            = smart
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:------------------------------------------------------
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:- Filespace locations
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:------------------------------------------------------
20140317:17:13:44:015303 gpinitstandby:mdw:gpadmin-[INFO]:-pg_system -> /data/master/gpseg-1
Do you want to continue with standby master initialization? Yy|Nn (default=N):
> y
20140317:17:13:49:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Syncing Greenplum Database extensions to standby
20140317:17:13:49:015303 gpinitstandby:mdw:gpadmin-[INFO]:-The packages on mdw2 are consistent.
20140317:17:13:49:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Stopping database...
20140317:17:14:18:015303 gpinitstandby:mdw:gpadmin-[INFO]:--n option given, skipping catalog update
20140317:17:14:18:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Forcing changed blocks to disk for filespace /data/master/gpseg-1...
20140317:17:14:18:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Copying filespace directory to mdw2
20140317:17:19:42:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Updating filespace flat files
20140317:17:19:42:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Updating filespace flat files
20140317:17:19:42:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Removing pg_hba.conf backup...
20140317:17:19:42:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Starting database in production mode...
20140317:17:20:14:015303 gpinitstandby:mdw:gpadmin-[INFO]:-Successfully syncronized standby master.
[gpadmin@mdw ~]$ 
[gpadmin@mdw ~]$ gpstate -f
20140317:17:21:03:016138 gpstate:mdw:gpadmin-[INFO]:-Starting gpstate with args: -f
20140317:17:21:03:016138 gpstate:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.2.5.0 build 1'
20140317:17:21:03:016138 gpstate:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.2.5.0 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Apr  5 2013 13:45:40'
20140317:17:21:03:016138 gpstate:mdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:-Standby master details
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:-----------------------
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:-   Standby address          = mdw2
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:-   Standby data directory   = /data/master/gpseg-1
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:-   Standby port             = 5432
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:-   Standby PID              = 23637
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:-   Standby status           = Standby host passive
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:--------------------------------------------------------------
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:--gp_master_mirroring table
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:--------------------------------------------------------------
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:--Summary state: Synchronized
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:--Detail state: 
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:--Log time: 2014-03-18 07:20:13+08
20140317:17:21:04:016138 gpstate:mdw:gpadmin-[INFO]:--------------------------------------------------------------
[gpadmin@mdw ~]$ 
greenplum常用运维命令
zyset
09-24 1608
备用节点重新恢复三连发 # 删除备节点 (-a 不需要用户确认) gpinitstandby -ra # 添加备节点 并 启动 (-a 不需要用户确认) gpinitstandby -as node1-prod-dataplatform-sciences.yonyouiuap.com # 启动备用节点 gpinitstandby -n 查看数据量大小 表大小 数据库大小 # 表大小 select pg_size_pretty(pg_relation_size('gp_test')); # 表和索引大小
修改GP系统表修复standby master
lijingkuan的博客
09-07 1442
事件缘由： 客户要求开发greenplum master高可用脚本，要实现master宕机的情况下，standby master被激活，接管业务。 但是在测试的过程中master切来切去，切乱了。 两个节点都是master，都能读写数据库。。。 即便杀掉第一个节点的master的进程，然后在第二个节点使用gpinitstandby -n 以启动的standby master的方式启动第一个...
Greenplum 实用工具-gpinitstandby
数据源的港湾
09-06 307
注：本文翻译自gpinitstandby工具用于为Greenplum Database系统添加和/或初始化备用协调器主机。
GreenPlum常用命令—gpstate/gpconfig/gpstart/gpstop/gprecoverseg/gpactivatestandby/gpinitstandby
Siaの码园
08-30 3938
GreenPlum常用命令—gpstate/gpconfig/gpstart/gpstop/gprecoverseg/gpactivatestandby/gpinitstandby1. gpstate2. gpconfig3. gpstart4. gpstop5. 集群恢复6. 激活备库流程7. 初始化备Master参考文档 1. gpstate 命令 参数 => 作用 gpstate -b => 显示简要状态 gpstate -c =&
故障分析 | Greenplum 集群 standby 故障处理
ActionTech的博客
12-06 850
客户测试环境Greenplum集群中，standby节点数据目录被误删除，导致standby节点不可用。如果此时由于其它各种原因导致master节点也不可用，则集群将无法对外提供服务，因此现需尽快恢复standby节点。1）库由Master Severs和Segment Severs组成。2）Master Server：3）Segment Severs：3.1、本地Greenplum集群环境：3.2、模拟master standby坏掉： 4、故障分析及解决： 4.1、检查状态： 可以看到：Standby
Greenplum实战--GreenPlum数据库Master节点搭建Standby【转】
murkey的专栏
04-20 808
GreenPlum数据库对于数据的冗余，也支持类似Oracle数据库物理DataGuard的数据冗余机制，Master的数据库镜像称为Standby，Segment节点的数据库镜像称之为Mirror，本文主要介绍如何为没有做Standby的Master节点添加Standby。 需要注意，在为Master节点搭建Standby的过程中，GreenPlum会自动关闭数据库，并以utility模式打开...
Greenplum如何开启、同步、删除Standby恢复原始Master
yimenglin的博客
03-12 1178
       在Master失效时，同步程序会停止，Standby可以被在本机被激活，激活Standby时，同步日志被用来恢复Master最后一次事务成功提交时的状态。在激活Standby时还可以指定一个新的Standby。 1. 激活Standby 现有环境原始primary master：mdw ，standby m...
[gpadmin@mdw1 root]$ gpstate -f 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-Starting gpstate with args: -f 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 6.10.0 build commit:cced3a78d1a0650ba21205438955d2df06644bc8' 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 9.4.24 (Greenplum Database 6.10.0 build commit:cced3a78d1a0650ba21205438955d2df06644bc8) on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 6.4.0, 64-bit compiled on Aug 7 2020 23:03:41' 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-Obtaining Segment details from master... 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-Standby master details 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:----------------------- 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:- Standby address = smdw1 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:- Standby data directory = /home/gpadmin/data/master/gpseg-1 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:- Standby port = 5432 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[WARNING]:-Standby PID = Error getting status from host smdw1 <<<<<<<< 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[WARNING]:-Standby status = Status could not be determined <<<<<<<< 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-------------------------------------------------------------- 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:--pg_stat_replication 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-------------------------------------------------------------- 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:--WAL Sender State: streaming 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:--Sync state: sync 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:--Sent Location: 0/C003D00 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:--Flush Location: 0/C003D00 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:--Replay Location: 0/C003D00 20250701:09:16:16:012799 gpstate:mdw1:gpadmin-[INFO]:-------------------------------------------------------------- [gpadmin@mdw1 root]$ gpinitstandby -n
07-02
gpinitstandby -s smdw1 # 重新初始化备用节点 ``` > **注意**：重新初始化会同步主节点数据到备用节点，确保有足够磁盘空间[^1] ##### 4. **处理Segment节点警告** ```bash gpssh -f all_segs -v -e 'ls $PGDATA/...
greeplum以工具模式连接Master
最新发布
07-25
之后 source /home/wad/.bashrec 在不同机器增加standby master节点（新版Greenplum已不支持-F选项，具体参考下方操作）gpinitstandby -F pg_system: /home/wad/mpp-data/master/gpseg-1 -s sdw2 gpinitstandby -s ...
can‘t import modules.please check that you have sourced greenplum_path.sh Detail: No module named
雅冰石的专栏
09-28 800
一 问题描述 执行gpconfig命令的时候报错： Cannot import modules. Please check that you have sourced greenplum_path.sh. Detail: No module named gppylib.gpparseopts 二 解决办法 source /home/greenplum/greenplum-db-5.0.0/greenplum_path.sh 再次执行gpconfig命令，不再报错了 ...
Greenplum数据库源码分析——Standby Master操作工具分析
肥叔菌的博客
08-01 1008
GreenplumStandby节点用于当Master节点损坏时提供Master服务。Standby实时与Master节点的Catalog和事务日志保持同步。在GreenplumStandbyMaster节点失效时，使用gpinitstandby命令配置一个新的Standby。在当前活动的Master主机上运行这个命令。。。在GreenplumStandbyMaster节点失效或不需要时，可以通过删除StandbyMaster节点。...
greenplum增加standby master节点
10-28
如何使用linux命令在Greenplum数据库上增加备份节点，包括本地备份数据和跨服务器备份数据。
Greenplum最佳实践
weixin_30329623的博客
07-05 419
一、最佳实践数据库参数部分 GP数据库参数配置 以下配置存于文件–postgresql.conf中，仅列出一些最常用的参数。 shared_buffers：刚开始可以设置一个较小的值，比如总内存的15%，然后逐渐增加，过程中监控性能提升和swap的情况。effective_cache_size : 这个参数告诉PostgreSQL的优化器有多少内存可以被用来缓存数据，以及帮助决定是...
Greenplum数据库故障分析——版本升级后gpstart -a为何返回失败
肥叔菌的博客
08-04 752
从上面日志可以看出在升级前HA组件在修复standbymaster，gpinitstandby运行到从master数据目录拷贝数据到standbymaster时，升级脚本关闭了greenplum集群，导致的失败。现场项目进行Greenplum数据库小版本升级时，升级脚本报错，提示数据库启动失败。在升级前HA组件在修复standbymaster，gpinitstandby运行到从master数据目录拷贝数据到standbymaster时，升级脚本关闭了greenplum集群，导致的失败。...
分布式数据库的高可用实现，Greenplum是如何做到的
Greenplum中文社区
07-03 563
什么是高可用 ...
greenplum 集群新增 standby节点
无锋剑
11-16 2041
greenplum 单独添加 standby 本文主要介绍如何为没有做Standby的Master节点添加Standby。（快速整理版） 旧版本gp集群需要注意！！！！ 在为Master节点搭建Standby的过程中，GreenPlum会自动关闭数据库，并以utility模式打开Master节点，然后修改gp_segment_configuration字典中增加Standby的信息，然后再关闭Ma...
Greenplum实战--添加standby master
murkey的专栏
04-19 1407
GreenPlum数据库对于数据的冗余，也支持类似Oracle数据库物理DataGuard的数据冗余机制，Master的数据库镜像称为Standby，Segment节点的数据库镜像称之为Mirror，本文主要介绍如何为没有做Standby的Master节点添加Standby。 需要注意，在为Master节点搭建Standby的过程中，GreenPlum会自动关闭数据库，并以utility模式打开...
greenplum 激活standby 和恢复 master 原有角色
学无止境
12-24 6180
定义：server1=(master) server2=(standby) Active standby server when master down.  gpactivatestandby -d /data/master/gpseg-1 -f (on server2) Change server1 as standby .   gpinitstandby -s server
greenplum恢复standby
朝着梦想 渐行前进
10-27 3101
greenplum恢复standby
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值