AI 助理
文档备案控制台
开发者社区 数据库 关系型数据库 文章 正文

Greenplum 添加或删除standby master节点

2015-12-21 12033
版权
版权声明：
本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《 阿里云开发者社区用户服务协议》和 《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写 侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
简介： 
Greenplum支持master节点的standby，如果你在初始化集群时没有创建standby节点，或者原来的standby节点坏了或者其他原因，要重搭standby。
本文将告诉你怎么做。
1. 如果要新建standby，但是原来已有standby，首先要删除它。
gpinitstandby -r 
如果原来的standby只是某种原因挂了，不需要删除，只需要重启，则使用以下命令来重启standby 
gpinitstandby -n

2. 如果搭建standby的机器不在原来的GP集群中，则需要将机器添加进来。
详细添加方法参考   http://yq.aliyun.com/articles/177  （本文不再重复，大致的内容如下）
   环境配置，例如OS kernel 参数；
   创建gp管理用户；
   ssh key的交换（使用gpssh-exkeys -e exist_hosts -x new_hosts）；
   greenplum bin软件的拷贝；
   使用gpcheck检查 (gpcheck -f new_hosts )；
   使用gpcheckperf检查性能 (gpcheckperf -f new_hosts_file -d /data1 -d /data2 -v)

3. 如果在GP已有集群中的机器中选择一台来搭建standby，则可以跳过第二步。
了解master节点用了哪些filespace.
postgres=# select a.dbid,a.content,a.role,a.port,a.hostname,b.fsname,c.fselocation from gp_segment_configuration a,pg_filespace b,pg_filespace_entry c where a.dbid=c.fsedbid and b.oid=c.fsefsoid order by content;
 dbid | content | role | port  |     hostname      |  fsname   |              fselocation              
------+---------+------+-------+-------------------+-----------+---------------------------------------
    1 |      -1 | p    |  1921 | digoal_host.sqa.zmf | pg_system | /disk1/digoal/gpdata/gpseg-1
    1 |      -1 | p    |  1921 | digoal_host.sqa.zmf | ssd1      | /disk1/digoal/new_p/gp-1
。。。。。。
了解master的即可，可以看到除了pg_system，还有一个filespace叫ssd1。

4. 进入初始化standby的步骤。
根据第三步查到的信息，规划standby master filespace数据目录；
$ mkdir /disk1/digoal/gpdata
$ mkdir /disk1/digoal/new_p

如果在不同的主机创建standby master，则建议使用同样的端口和目录结构。
如下：
$gpinitstandby -F pg_system:/data01/gpdata/master_pgdata/gpseg-1 -s digoal_host199092.zmf 
20151221:14:17:24:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Validating environment and parameters for standby initialization...
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Checking for filespace directory /data01/gpdata/master_pgdata/gpseg-1 on digoal_host199092.zmf
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:------------------------------------------------------
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum standby master initialization parameters
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:------------------------------------------------------
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum master hostname               = digoal_host193096.zmf
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum master data directory         = /data01/gpdata/master_pgdata/gpseg-1
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum master port                   = 1921
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum standby master hostname       = digoal_host199092.zmf
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum standby master port           = 1921
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum standby master data directory = /data01/gpdata/master_pgdata/gpseg-1
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Greenplum update system catalog         = On
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:------------------------------------------------------
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:- Filespace locations
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:------------------------------------------------------
20151221:14:17:25:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-pg_system -> /data01/gpdata/master_pgdata/gpseg-1
Do you want to continue with standby master initialization? Yy|Nn (default=N):
> y
20151221:14:26:46:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Syncing Greenplum Database extensions to standby
20151221:14:26:46:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-The packages on digoal_host199092.zmf are consistent.
20151221:14:26:46:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Adding standby master to catalog...
20151221:14:26:46:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Database catalog updated successfully.
20151221:14:26:47:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Updating pg_hba.conf file...
20151221:14:26:52:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-pg_hba.conf files updated successfully.
20151221:14:26:56:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Updating filespace flat files...
20151221:14:26:56:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Filespace flat file updated successfully.
20151221:14:26:56:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Starting standby master
20151221:14:26:56:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Checking if standby master is running on host: digoal_host199092.zmf  in directory: /data01/gpdata/master_pgdata/gpseg-1
20151221:14:27:00:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Cleaning up pg_hba.conf backup files...
20151221:14:27:06:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Backup files of pg_hba.conf cleaned up successfully.
20151221:14:27:06:012334 gpinitstandby:digoal_host193096:digoal-[INFO]:-Successfully created standby master on digoal_host199092.zmf

digoal=# select * from gp_segment_configuration where content='-1';
 dbid | content | role | preferred_role | mode | status | port |     hostname      |      address      | replication_port | san_mounts 
------+---------+------+----------------+------+--------+------+-------------------+-------------------+------------------+------------
    1 |      -1 | p    | p              | s    | u      | 1921 | digoal_host193096.zmf | digoal_host193096.zmf |                  | 
   26 |      -1 | m    | m              | s    | u      | 1921 | digoal_host199092.zmf | digoal_host199092.zmf |                  | 
(2 rows)

如果在同一台主机创建standby master，则需要使用不同的端口和目录结构。
如下：
指定不同的filespace路径，不同的监听端口。
$gpinitstandby -F pg_system:/disk1/digoal/gpdata/gpseg-2,ssd1:/disk1/digoal/new_p/gp-2 -P 1922 -s digoal_host.sqa.zmf
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Validating environment and parameters for standby initialization...
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Checking for filespace directory /disk1/digoal/gpdata/gpseg-2 on digoal_host.sqa.zmf
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Checking for filespace directory /disk1/digoal/new_p/gp-2 on digoal_host.sqa.zmf
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:------------------------------------------------------
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum standby master initialization parameters
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:------------------------------------------------------
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum master hostname               = digoal_host.sqa.zmf
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum master data directory         = /disk1/digoal/gpdata/gpseg-1
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum master port                   = 1921
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum standby master hostname       = digoal_host.sqa.zmf
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum standby master port           = 1922
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum standby master data directory = /disk1/digoal/gpdata/gpseg-2
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Greenplum update system catalog         = On
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:------------------------------------------------------
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:- Filespace locations
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:------------------------------------------------------
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-pg_system -> /disk1/digoal/gpdata/gpseg-2
20151221:14:34:01:077652 gpinitstandby:digoal_host:digoal-[INFO]:-ssd1 -> /disk1/digoal/new_p/gp-2
Do you want to continue with standby master initialization? Yy|Nn (default=N):
> y
20151221:14:34:03:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Syncing Greenplum Database extensions to standby
20151221:14:34:03:077652 gpinitstandby:digoal_host:digoal-[INFO]:-The packages on digoal_host.sqa.zmf are consistent.
20151221:14:34:03:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Adding standby master to catalog...
20151221:14:34:04:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Database catalog updated successfully.
20151221:14:34:05:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Updating pg_hba.conf file...
20151221:14:34:13:077652 gpinitstandby:digoal_host:digoal-[INFO]:-pg_hba.conf files updated successfully.
20151221:14:34:31:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Updating filespace flat files...
20151221:14:34:31:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Writing standby information to /disk1/digoal/gpdata/gpseg-1/gp_transaction_files_filespace flat file
20151221:14:34:32:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Writing standby information to /disk1/digoal/gpdata/gpseg-1/gp_temporary_files_filespace flat file
20151221:14:34:32:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Filespace flat file updated successfully.
20151221:14:34:32:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Starting standby master
20151221:14:34:32:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Checking if standby master is running on host: digoal_host.sqa.zmf  in directory: /disk1/digoal/gpdata/gpseg-2
20151221:14:36:16:077652 gpinitstandby:digoal_host:digoal-[WARNING]:-Could not start standby master
20151221:14:36:16:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Cleaning up pg_hba.conf backup files...
20151221:14:36:21:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Backup files of pg_hba.conf cleaned up successfully.
20151221:14:36:21:077652 gpinitstandby:digoal_host:digoal-[INFO]:-Successfully created standby master on digoal_host.sqa.zmf

启动standby
$gpinitstandby -n
20151221:14:39:40:085625 gpinitstandby:digoal_host:digoal-[INFO]:-Starting standby master
20151221:14:39:40:085625 gpinitstandby:digoal_host:digoal-[INFO]:-Checking if standby master is running on host: digoal_host.sqa.zmf  in directory: /disk1/digoal/gpdata/gpseg-2

查看standby延迟，查看pg_stat_replication 视图即可。
digoal=# select pg_switch_xlog();
 pg_switch_xlog 
----------------
 0/C0000D8
(1 row)
digoal=# select * from pg_stat_replication ;
 procpid | usesysid | usename  | application_name |  client_addr  | client_port |         backend_start         |   state   | sent_location | write_location | flush_location | replay_location | sync_priority | sync_state 
---------+----------+----------+------------------+---------------+-------------+-------------------------------+-----------+---------------+----------------+----------------+-----------------+---------------+------------
   13444 |       10 | dege.zzz | walreceiver      | 100.69.199.92 |       47792 | 2015-12-21 14:27:00.164785+08 | streaming | 0/D080000     | 0/CC00000      | 0/C880000      | 0/C0000B8       |             1 | sync
(1 row)
...
digoal=# select * from pg_stat_replication ;
 procpid | usesysid | usename  | application_name |  client_addr  | client_port |         backend_start         |   state   | sent_location | write_location | flush_location | replay_location | sync_priority | sync_state 
---------+----------+----------+------------------+---------------+-------------+-------------------------------+-----------+---------------+----------------+----------------+-----------------+---------------+------------
   13444 |       10 | dege.zzz | walreceiver      | 100.69.199.92 |       47792 | 2015-12-21 14:27:00.164785+08 | streaming | 0/10000000    | 0/10000000     | 0/10000000     | 0/10000000      |             1 | sync
(1 row)
参考
gpinitstandby -?
德哥
目录
相关文章
GG2020gg
|
机器学习/深度学习 运维 Linux
KVM详解（二）——KVM安装部署
KVM详解（二）——KVM安装部署
GG2020gg
993 3
芦熙霖
|
5月前
|
供应链 安全 前端开发
2026 年新型网络威胁演进与防御体系研究 —— 以两起典型攻击为例
本文剖析2026年ShinyHunters入侵Canvas与Play勒索软件利用CLFS零日漏洞两大典型事件，揭示供应链攻击、身份劫持、零日武器化、双重勒索等新威胁特征；提出以身份为中心、零信任为基座的五层防御体系，并提供可落地的令牌校验、提权检测、数据导出监控等代码实现，助力教育、金融等行业构建韧性安全防线。（239字）
芦熙霖
1052 8
9589
|
5月前
|
缓存 并行计算 数据可视化
C++在量化交易回测系统中的运用（性能与正确性并重）
量化交易策略在实盘前，必须用历史数据验证其表现（收益、最大回撤、夏普比率）。回测系统接收数年的tick级数据（每秒数千笔），逐笔模拟订单成交，统计指标。
9589
402 0
1632789041684035
|
10月前
|
Linux 编译器 数据安全/隐私保护
gcc-c++-7.3.0 rpm安装方法 Linux麒麟KY10完整步骤
本文介绍在麒麟系统中手动安装 GCC C++ 编译器的完整步骤。从下载 RPM 安装包、确认文件路径，到使用终端通过 `yum` 或 `rpm` 命令安装，涵盖权限处理、依赖解决及版本冲突等常见问题，并提供验证安装方法，确保 `g++` 成功配置。
1632789041684035
2141 1
winx_19970108018
|
搜索推荐 API 开发者
京东商品详情优惠券API接口全攻略
京东商品详情优惠券API接口为电商开发者和商家提供了精准查询、获取详细信息及实时监测优惠券状态的功能。通过商品ID，可筛选出特定商品的定向或店铺通用优惠券，获取面额、使用门槛、领取条件等详尽信息，并监测优惠券的领取情况。该接口支持多种筛选参数，满足个性化需求，助力电商业务拓展与创新。示例代码展示了如何使用Python调用此接口，实现优惠券信息的高效获取。
winx_19970108018
1408 23
zuozewei
|
存储 Kubernetes 网络协议
Kubernetes 集群部署 NFS-Subdir-External-Provisioner 存储插件
Kubernetes 对 Pod 进行调度时，以当时集群中各节点的可用资源作为主要依据，自动选择某一个可用的节点，并将 Pod 分配到该节点上。在这种情况下，Pod 中容器数据的持久化如果存储在所在节点的磁盘上，就会产生不可预知的问题，例如，当 Pod 出现故障，Kubernetes 重新调度之后，Pod 所在的新节点上，并不存在上一次 Pod 运行时所在节点上的数
zuozewei
9864 3
Kubernetes 集群部署 NFS-Subdir-External-Provisioner 存储插件
蚝油菜花
|
机器学习/深度学习 人工智能
Qwen2VL-Flux：开源的多模态图像生成模型，支持多种生成模式
Qwen2VL-Flux 是一个开源的多模态图像生成模型，结合了 Qwen2VL 的视觉语言理解和 FLUX 框架，能够基于文本提示和图像参考生成高质量的图像。该模型支持多种生成模式，包括变体生成、图像到图像转换、智能修复及 ControlNet 引导生成，具备深度估计和线条检测功能，提供灵活的注意力机制和高分辨率输出，是一站式的图像生成解决方案。
蚝油菜花
1951 4
Qwen2VL-Flux：开源的多模态图像生成模型，支持多种生成模式
技术小甜
|
Linux NoSQL Redis
操作系统内存配置overcommit_memory
技术小甜
3969 0
html的七十二变
|
前端开发 JavaScript 开发者
html<p>标签的用法
`&lt;p&gt;` 标签主要用于定义段落，但在网页设计中也有创新用法，如用作容器、自定义样式、响应式设计调整、嵌套结构创建、伪元素及伪类应用、添加微数据和属性，以及增强可访问性等，这些方法可在保证语义清晰的前提下提升页面表现力。
html的七十二变
1087 10
游客ot6eft3qn37ga
|
存储 JavaScript 前端开发
小白实战！用JS实现一个3D翻书效果，附上代码
小白实战！用JS实现一个3D翻书效果，附上代码
游客ot6eft3qn37ga
2029 5
数据库

关系型数据库

热门文章

最新文章

  • 1
    什么场景应该用 MongoDB ？
  • 2
    Linux 性能诊断 perf使用指南
  • 3
    PostgreSQL 9.5+ 高效分区表实现 - pg_pathman
  • 4
    时序数据库分析 - TimescaleDB时序数据库介绍
  • 5
    从MySQL导出到PostgreSQL
  • 6
    阿里云数据库CloudDBA智慧解决数据库性能优化和问题诊断难题
  • 7
    数据库案例集锦 - 开发者的《如来神掌》
  • 8
    PostgreSQL 聚合函数讲解 - 1 常用聚合函数
  • 9
    开源数据库PostgreSQL攻克并行计算难题
  • 10
    Greenplum 添加或删除standby master节点
  • 1
    【赵渝强老师】崖山数据库的命令行客户端工具
    27
  • 2
    复跑闭环工程论——上游共创理论·下游智能体修正复跑即可察觉
    25
  • 3
    【赵渝强老师】高斯数据库（openGauss）的服务器日志文件
    26
  • 4
    一文读懂阿里云RDS新版：核心能力、底层架构与上手指南
    46
  • 5
    【赵渝强老师】国产崖山数据库的行号：ROWNUM
    102
  • 6
    【赵渝强老师】Oracle查询结果集的行号 ROWNUM 详解
    85
  • 7
    【赵渝强老师】崖山数据库的行地址ROWID
    101
  • 8
    MySQL InnoDB 并发控制核心原理：事务、隔离级别、MVCC 与锁机制
    223
  • 9
    MySQL索引为什么必须用B+树？从磁盘IO深度推导
    210
  • 10
    IvorySQL 在阿里云上验证 Oracle 兼容性：UTL_URL.ESCAPE/UNESCAPE 与 SYS_CONTEXT
    166

    • 相关电子书

    更多
  • 低代码开发师（初级）实战教程
  • 冬季实战营第三期：MySQL数据库进阶实战
  • 阿里巴巴DevOps 最佳实践手册
    • 下一篇
    一条命令迁移，帮你实现 OpenClaw 与 Hermes Agent 记忆互通！