Greenplum 数据库 Master ： GP 的控制节点/实例 Standby ： GP 的备用控制节点/实例 Host(主机) ： GP 的一台独立的机器设备 Instance ： GP 的计算实例，很多时候也叫 Segment Primary ： GP 的主计算实例 Mirror ： GP 的镜像计算实例 MPP ： 大规模并行处理 .................................................................................. - 12 - 计算实例：Instance ............................................................................................... ......................... - 15 - Instance 镜像........................................................................................................ - 15 - Instance 故障切换与恢复 .........................

Segment Instance Segment Instance Segment Instance Segment Instance Segment Host Segment Instance Segment Instance Segment Instance Segment Instance Segment Host Segment Instance Segment Instance Segment Segment Instance Segment Instance Segment Host Segment Instance Segment Instance Segment Instance Segment Instance query Load Master节点和Standby Master节点 Greenplum 架构 Interconnect高速网络 Segment主机部署多个Segment实例 Mirroring部署方案 Segment Instance Segment host 1 Segment 1 (Primary) Segment Instance Segment 2 (Primary) Segment Instance Segment host 2 Segment 3 (Primary) Segment Instance Segment 4 (Primary)

Examples for Creating External Tables 0 Example 1—Single gpfdist instance on single-NIC machine 797 Example 1—Single gpfdist instance on single-NIC machine 0 Example 2—Multiple gpfdist instances 797 Example 3—Multiple gpfdists instances 0 Example 4—Single gpfdist instance with error logging 798 Example 4—Single gpfdist instance with error logging 0 Example 5—TEXT Format on a Hadoop Distributed Disk Space Requirements 150MB per host for Greenplum installation Approximately 300MB per segment instance for metadata Cap disk capacity at 70% full to accommodate temporary files and prevent performance

Example 1—Single gpfdist instance on single-NIC machine 637 Example 2—Multiple gpfdist instances 637 Example 3—Multiple gpfdists instances 637 Example 4—Single gpfdist instance with error logging 637 error. Cluster Management 32190 : Resolved an issue where gprecoverseg failed to detect than an instance of pg_basebackup was already running, which led to the corruption of the data directory and a PANIC issue where running an internal function on a partition table caused the master Greenplum Database instance to crash. 32500 Resolved an issue introduced in Greenplum Database 6.21.0 where the error "PANIC"

Examples for Creating External Tables 0 Example 1—Single gpfdist instance on single-NIC machine 806 Example 1—Single gpfdist instance on single-NIC machine 0 Example 2—Multiple gpfdist instances 806 Example 3—Multiple gpfdists instances 0 Example 4—Single gpfdist instance with error logging 807 Example 4—Single gpfdist instance with error logging 0 Example 5—TEXT Format on a Hadoop Distributed Disk Space Requirements 150MB per host for Greenplum installation Approximately 300MB per segment instance for metadata Cap disk capacity at 70% full to accommodate temporary files and prevent performance

Example 1—Single gpfdist instance on single-NIC machine 630 Example 2—Multiple gpfdist instances 630 Example 3—Multiple gpfdists instances 631 Example 4—Single gpfdist instance with error logging 631 error. Cluster Management 32190 Resolved an issue where gprecoverseg failed to detect than an instance of pg_basebackup was already running, which led to the corruption of the data directory and a PANIC issue where running an internal function on a partition table caused the master Greenplum Database instance to crash. 32500 Resolved an issue introduced in Greenplum Database 6.21.0 where the error "PANIC"

Example 1—Single gpfdist instance on single-NIC machine 607 Example 2—Multiple gpfdist instances 608 Example 3—Multiple gpfdists instances 608 Example 4—Single gpfdist instance with error logging 608 error. Cluster Management 32190 : Resolved an issue where gprecoverseg failed to detect than an instance of pg_basebackup was already running, which led to the corruption of the data directory and a PANIC issue where running an internal function on a partition table caused the master Greenplum Database instance to crash. 32500 Resolved an issue introduced in Greenplum Database 6.21.0 where the error "PANIC"

Example 1—Single gpfdist instance on single-NIC machine 608 Example 2—Multiple gpfdist instances 608 Example 3—Multiple gpfdists instances 608 Example 4—Single gpfdist instance with error logging 608 error. Cluster Management 32190 Resolved an issue where gprecoverseg failed to detect than an instance of pg_basebackup was already running, which led to the corruption of the data directory and a PANIC issue where running an internal function on a partition table caused the master Greenplum Database instance to crash. 32500 Resolved an issue introduced in Greenplum Database 6.21.0 where the error "PANIC"

Example 1—Single gpfdist instance on single-NIC machine 605 Example 2—Multiple gpfdist instances 605 Example 3—Multiple gpfdists instances 605 Example 4—Single gpfdist instance with error logging 606 issue where running an internal function on a partition table caused the master Greenplum Database instance to crash. 32500 Resolved an issue introduced in Greenplum Database 6.21.0 where the error "PANIC" temp_tablespaces. 31617 - Resource Groups A database instance was failing to start up, with the message Command pg_ctl reports Master gdm instance active because a mirror segment couldn't be recovered

Example 1—Single gpfdist instance on single-NIC machine 518 Example 2—Multiple gpfdist instances 518 Example 3—Multiple gpfdists instances 518 Example 4—Single gpfdist instance with error logging 519 temp_tablespaces. 31617 - Resource Groups A database instance was failing to start up, with the message Command pg_ctl reports Master gdm instance active because a mirror segment couldn’t be recovered temp table with DISTRIBUTED RANDOMLY from a DISTRIBUTED REPLICATED table put all records into one instance when the query optimizer was enabled. This issue was resolved by adding the necessary logic to