{"id":31478,"date":"2024-02-29T13:11:05","date_gmt":"2024-02-29T12:11:05","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=31478"},"modified":"2024-02-29T13:11:07","modified_gmt":"2024-02-29T12:11:07","slug":"getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/","title":{"rendered":"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster"},"content":{"rendered":"\n

In the last post<\/a> we’ve configured the operating system for Greenplum and completed the installation. In this post we’ll create the so called “Data Storage Areas” (which is just a mount point or directory) and initialize the cluster. All the work is performed on the “Coordinator Host” and “gpssh” is used to perform the work on the remote systems.<\/p>\n\n\n\n

For this playground environment we’ll just use a directory for the storage area. In a real setup you should of course use a dedicated, separate mount point. We start on the coordinator node:<\/p>\n\n\n

\n[gpadmin@rocky9-gp7-master ~]$ sudo mkdir -p \/data\/coordinator\n[gpadmin@rocky9-gp7-master ~]$ sudo chown gpadmin:gpadmin \/data\/coordinator\/\n<\/pre><\/div>\n\n\n
Using “gpssh” we do the same on the two segment hosts:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpssh -h rocky9-gp7-segment1 -e "sudo mkdir -p \/data\/coordinator"\n[rocky9-gp7-segment1] sudo mkdir -p \/data\/coordinator\n[gpadmin@rocky9-gp7-master ~]$ gpssh -h rocky9-gp7-segment2 -e "sudo mkdir -p \/data\/coordinator"\n[rocky9-gp7-segment2] sudo mkdir -p \/data\/coordinator\n[gpadmin@rocky9-gp7-master ~]$ gpssh -h rocky9-gp7-segment1 -e "sudo chown gpadmin:gpadmin \/data\/coordinator\/"\n[rocky9-gp7-segment1] sudo chown gpadmin:gpadmin \/data\/coordinator\/\n[gpadmin@rocky9-gp7-master ~]$ gpssh -h rocky9-gp7-segment2 -e "sudo chown gpadmin:gpadmin \/data\/coordinator\/"\n[rocky9-gp7-segment2] sudo chown gpadmin:gpadmin \/data\/coordinator\/\n<\/pre><\/div>\n\n\n
This storage area is used to store system catalog tables and metadata. It is not used to store any user data.<\/p>\n\n\n\n
The storage areas on the segment hosts will store user data, so they need to be bigger. All of the segment nodes should provide a storage area for the so called “primary segments”. Those segments are the active ones and will be used by default for serving client requests. In addition there should be a storage area for so called “mirror segments”. Those segments will be used in case the primary segment becomes unavailable. For that reason a mirror segment must always be on another host than it’s primary segment (more on that later).<\/p>\n\n\n\n
Before we use “gpssh” to do this, let’s create a file which only contains the host names of the segment hosts:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ echo "rocky9-gp7-segment1\nrocky9-gp7-segment2" > ~\/hostfile_gpssh_segonly\n<\/pre><\/div>\n\n\n
Having this in place we can easily create the directories on the segment nodes:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpssh -f hostfile_gpssh_segonly -e 'sudo mkdir -p \/data\/primary'\n[rocky9-gp7-segment1] sudo mkdir -p \/data\/primary\n[rocky9-gp7-segment2] sudo mkdir -p \/data\/primary\n[gpadmin@rocky9-gp7-master ~]$ gpssh -f hostfile_gpssh_segonly -e 'sudo mkdir -p \/data\/mirror'\n[rocky9-gp7-segment1] sudo mkdir -p \/data\/mirror\n[rocky9-gp7-segment2] sudo mkdir -p \/data\/mirror\n[gpadmin@rocky9-gp7-master ~]$ gpssh -f hostfile_gpssh_segonly -e 'sudo chown gpadmin:gpadmin \/data\/*'\n[rocky9-gp7-segment2] sudo chown gpadmin:gpadmin \/data\/*\n[rocky9-gp7-segment1] sudo chown gpadmin:gpadmin \/data\/*\n<\/pre><\/div>\n\n\n
Greenplum comes with a utility can you can use to validate your systems when it comes to network, disk and memory performance. The utility is called “gpcheckperf” and this, e.g., will run a network performance test:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpcheckperf -f hostfile_exkeys -r N -d \/tmp\n[INFO] --buffer-size value is not specified or invalid. Using default (8 kilobytes)\n\/usr\/local\/greenplum-db-7.1.0\/bin\/gpcheckperf -f hostfile_exkeys -r N -d \/tmp\n-------------------\n--  NETPERF TEST\n-------------------\n\n====================\n==  RESULT 2024-02-28T16:41:39.049314\n====================\nNetperf bisection bandwidth test\nrocky9-gp7-master -&gt; rocky9-gp7-segment1 = 1971.150000\nrocky9-gp7-segment2 -&gt; rocky9-gp7-master = 1688.660000\nrocky9-gp7-segment1 -&gt; rocky9-gp7-master = 1310.830000\nrocky9-gp7-master -&gt; rocky9-gp7-segment2 = 1377.070000\n\nSummary:\nsum = 6347.71 MB\/sec\nmin = 1310.83 MB\/sec\nmax = 1971.15 MB\/sec\navg = 1586.93 MB\/sec\nmedian = 1688.66 MB\/sec\n\n[Warning] connection between rocky9-gp7-segment2 and rocky9-gp7-master is no good\n[Warning] connection between rocky9-gp7-segment1 and rocky9-gp7-master is no good\n[Warning] connection between rocky9-gp7-master and rocky9-gp7-segment2 is no good\n<\/pre><\/div>\n\n\n
I don’t care about this warnings because this is just a test, you should care if you do a real setup, of course. Running a disk I\/O test can  be done like this (this will run dd<\/a> tests on all the segment nodes):<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpcheckperf -f hostfile_gpssh_segonly -r ds -D -d \/data\/primary -d \/data\/mirror\n[INFO] --buffer-size value is not specified or invalid. Using default (8 kilobytes)\n\/usr\/local\/greenplum-db-7.1.0\/bin\/gpcheckperf -f hostfile_gpssh_segonly -r ds -D -d \/data\/primary -d \/data\/mirror\n[Warning] Using 7650140160 bytes for disk performance test. This might take some time\n--------------------\n--  DISK WRITE TEST\n--------------------\n--------------------\n--  DISK READ TEST\n--------------------\n--------------------\n--  STREAM TEST\n--------------------\n\n====================\n==  RESULT 2024-02-28T16:49:58.607351\n====================\n\n disk write avg time (sec): 109.30\n disk write tot bytes: 15300296704\n disk write tot bandwidth (MB\/s): 133.51\n disk write min bandwidth (MB\/s): 66.31 [rocky9-gp7-segment1]\n disk write max bandwidth (MB\/s): 67.19 [rocky9-gp7-segment2]\n -- per host bandwidth --\n    disk write bandwidth (MB\/s): 66.31 [rocky9-gp7-segment1]\n    disk write bandwidth (MB\/s): 67.19 [rocky9-gp7-segment2]\n\n\n disk read avg time (sec): 58.48\n disk read tot bytes: 15300296704\n disk read tot bandwidth (MB\/s): 250.04\n disk read min bandwidth (MB\/s): 119.41 [rocky9-gp7-segment1]\n disk read max bandwidth (MB\/s): 130.63 [rocky9-gp7-segment2]\n -- per host bandwidth --\n    disk read bandwidth (MB\/s): 130.63 [rocky9-gp7-segment2]\n    disk read bandwidth (MB\/s): 119.41 [rocky9-gp7-segment1]\n\n\n stream tot bandwidth (MB\/s): 66240.30\n stream min bandwidth (MB\/s): 32732.80 [rocky9-gp7-segment1]\n stream max bandwidth (MB\/s): 33507.50 [rocky9-gp7-segment2]\n -- per host bandwidth --\n    stream bandwidth (MB\/s): 32732.80 [rocky9-gp7-segment1]\n    stream bandwidth (MB\/s): 33507.50 [rocky9-gp7-segment2]\n\n<\/pre><\/div>\n\n\n
Assuming that we’re happy with the performance statistics we can proceed and initialize the cluster. With a community PostgreSQL installation you would do this with initdb<\/a>, and actually initdb and many other utilities you know from PostgreSQL are available on the system:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ ls -la \/usr\/local\/greenplum-db\/bin\/\ntotal 81796\ndrwxr-xr-x  8 gpadmin gpadmin     4096 Feb 28 16:36 .\ndrwxr-xr-x 11 gpadmin gpadmin     4096 Feb 28 14:52 ..\n-rwxr-xr-x  1 gpadmin gpadmin    66665 Feb  8 21:01 analyzedb\n-rwxr-xr-x  1 gpadmin gpadmin   259104 Feb  8 21:01 clusterdb\n-rwxr-xr-x  1 gpadmin gpadmin   254416 Feb  8 21:01 createdb\n-rwxr-xr-x  1 gpadmin gpadmin   265176 Feb  8 21:01 createuser\n-rwxr-xr-x  1 gpadmin gpadmin   238480 Feb  8 21:01 dropdb\n-rwxr-xr-x  1 gpadmin gpadmin   238352 Feb  8 21:01 dropuser\n-rwxr-xr-x  1 gpadmin gpadmin  2754648 Feb  8 21:01 ecpg\n-rwxr-xr-x  1 gpadmin gpadmin    17248 Feb  8 21:01 gpactivatestandby\n-rwxr-xr-x  1 gpadmin gpadmin      494 Feb  8 21:01 gpaddmirrors\n-rwxr-xr-x  1 gpadmin gpadmin   137764 Feb  8 21:01 gpcheckcat\ndrwxr-xr-x  3 gpadmin gpadmin     4096 Feb 28 14:52 gpcheckcat_modules\n-rwxr-xr-x  1 gpadmin gpadmin    29980 Feb  8 21:01 gpcheckperf\n-rwxr-xr-x  1 gpadmin gpadmin     6682 Feb  8 21:01 gpcheckresgroupimpl\n-rwxr-xr-x  1 gpadmin gpadmin     3230 Feb  8 21:01 gpcheckresgroupv2impl\n-rwxr-xr-x  1 gpadmin gpadmin    23374 Feb  8 21:01 gpconfig\ndrwxr-xr-x  3 gpadmin gpadmin     4096 Feb 28 14:52 gpconfig_modules\n-rwxr-xr-x  1 gpadmin gpadmin    13754 Feb  8 21:01 gpdeletesystem\n-rwxr-xr-x  1 gpadmin gpadmin   114969 Feb  8 21:01 gpexpand\n-rwxr-xr-x  1 gpadmin gpadmin   407208 Feb  8 21:01 gpfdist\n-rwxr-xr-x  1 gpadmin gpadmin    34959 Feb  8 21:01 gpinitstandby\n-rwxr-xr-x  1 gpadmin gpadmin    83564 Feb  8 21:01 gpinitsystem\n-rwxr-xr-x  1 gpadmin gpadmin      189 Feb  8 21:01 gpload\n-rw-r--r--  1 gpadmin gpadmin      202 Feb  8 21:01 gpload.bat\n-rwxr-xr-x  1 gpadmin gpadmin   113900 Feb  8 21:01 gpload.py\n-rwxr-xr-x  1 gpadmin gpadmin    21018 Feb  8 21:01 gplogfilter\n-rwxr-xr-x  1 gpadmin gpadmin    15333 Feb  8 21:01 gpmemreport\n-rwxr-xr-x  1 gpadmin gpadmin     8032 Feb  8 21:01 gpmemwatcher\n-rwxr-xr-x  1 gpadmin gpadmin    21646 Feb  8 21:01 gpmovemirrors\n-rwxr-xr-x  1 gpadmin gpadmin      548 Feb  8 21:01 gprecoverseg\n-rwxr-xr-x  1 gpadmin gpadmin     1162 Feb  8 21:01 gpreload\n-rwxr-xr-x  1 gpadmin gpadmin    10723 Feb  8 21:01 gpsd\n-rwxr-xr-x  1 gpadmin gpadmin     9258 Feb  8 21:01 gpssh\n-rwxr-xr-x  1 gpadmin gpadmin    32516 Feb  8 21:01 gpssh-exkeys\ndrwxr-xr-x  3 gpadmin gpadmin       70 Feb 28 14:52 gpssh_modules\n-rwxr-xr-x  1 gpadmin gpadmin    37579 Feb  8 21:01 gpstart\n-rwxr-xr-x  1 gpadmin gpadmin      422 Feb  8 21:01 gpstate\n-rwxr-xr-x  1 gpadmin gpadmin    45588 Feb  8 21:01 gpstop\n-rwxr-xr-x  1 gpadmin gpadmin     4074 Feb  8 21:01 gpsync\n-rwxr-xr-x  1 gpadmin gpadmin   528656 Feb  8 21:01 initdb\ndrwxr-xr-x  4 gpadmin gpadmin     4096 Feb 28 14:52 lib\n-rwxr-xr-x  1 gpadmin gpadmin    17611 Feb  8 21:01 minirepro\n-rwxr-xr-x  1 gpadmin gpadmin   163568 Feb  8 21:01 pg_archivecleanup\n-rwxr-xr-x  1 gpadmin gpadmin   459656 Feb  8 21:01 pg_basebackup\n-rwxr-xr-x  1 gpadmin gpadmin   667784 Feb  8 21:01 pgbench\n-rwxr-xr-x  1 gpadmin gpadmin   224176 Feb  8 21:01 pg_checksums\n-rwxr-xr-x  1 gpadmin gpadmin   150736 Feb  8 21:01 pg_config\n-rwxr-xr-x  1 gpadmin gpadmin   177072 Feb  8 21:01 pg_controldata\n-rwxr-xr-x  1 gpadmin gpadmin   235296 Feb  8 21:01 pg_ctl\n-rwxr-xr-x  1 gpadmin gpadmin  1591264 Feb  8 21:01 pg_dump\n-rwxr-xr-x  1 gpadmin gpadmin   371784 Feb  8 21:01 pg_dumpall\n-rwxr-xr-x  1 gpadmin gpadmin   239264 Feb  8 21:01 pg_isready\n-rwxr-xr-x  1 gpadmin gpadmin   327200 Feb  8 21:01 pg_receivewal\n-rwxr-xr-x  1 gpadmin gpadmin   331168 Feb  8 21:01 pg_recvlogical\n-rwxr-xr-x  1 gpadmin gpadmin   211880 Feb  8 21:01 pg_resetwal\n-rwxr-xr-x  1 gpadmin gpadmin   764392 Feb  8 21:01 pg_restore\n-rwxr-xr-x  1 gpadmin gpadmin   480400 Feb  8 21:01 pg_rewind\n-rwxr-xr-x  1 gpadmin gpadmin   171944 Feb  8 21:01 pg_test_fsync\n-rwxr-xr-x  1 gpadmin gpadmin   144336 Feb  8 21:01 pg_test_timing\n-rwxr-xr-x  1 gpadmin gpadmin   606048 Feb  8 21:01 pg_upgrade\n-rwxr-xr-x  1 gpadmin gpadmin   454504 Feb  8 21:01 pg_waldump\n-rwxr-xr-x  1 gpadmin gpadmin 67633848 Feb  8 21:01 postgres\nlrwxrwxrwx  1 gpadmin gpadmin        8 Feb  8 21:01 postmaster -> postgres\n-rwxr-xr-x  1 gpadmin gpadmin  1826136 Feb  8 21:01 psql\ndrwxr-xr-x  2 gpadmin gpadmin       35 Feb 28 14:52 __pycache__\n-rwxr-xr-x  1 gpadmin gpadmin   267224 Feb  8 21:01 reindexdb\ndrwxr-xr-x  2 gpadmin gpadmin       20 Feb 28 14:52 stream\n-rwxr-xr-x  1 gpadmin gpadmin   287832 Feb  8 21:01 vacuumdb\n<\/pre><\/div>\n\n\n
The Greenplum system will work across multiple nodes and all of them will host PostgreSQL instances (called segment and coordinator instances). To make this easier to setup Greenplum comes with its own version of “initdb” which is called “gpinitsystem”:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpinitsystem --version\ngpinitsystem 7.1.0 build commit:e7c2b1f14bb42a1018ac57d14f4436880e0a0515 Open Source\n<\/pre><\/div>\n\n\n
Before the system can be initialized we need to create the Greenplum database configuration file. There is a template we can use as a starting point:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ echo $GPHOME\n\/usr\/local\/greenplum-db-7.1.0\n[gpadmin@rocky9-gp7-master ~]$ mkdir \/home\/gpadmin\/gpconfigs\/\n[gpadmin@rocky9-gp7-master ~]$ cp $GPHOME\/docs\/cli_help\/gpconfigs\/gpinitsystem_config \/home\/gpadmin\/gpconfigs\/gpinitsystem_config\n[gpadmin@rocky9-gp7-master ~]$ vi \/home\/gpadmin\/gpconfigs\/gpinitsystem_config\n<\/pre><\/div>\n\n\n
For the scope of this demo system all which needs to be adjusted are the data and mirror directories:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ egrep "DATA_DIRECTORY|MIRROR_DATA_DIRECTORY|MIRROR_PORT_BASE" \/home\/gpadmin\/gpconfigs\/gpinitsystem_config | egrep -v "^#"\ndeclare -a DATA_DIRECTORY=(\/data\/primary)\nMIRROR_PORT_BASE=7000\ndeclare -a MIRROR_DATA_DIRECTORY=(\/data\/mirror)\n<\/pre><\/div>\n\n\n
This config and the hosts file which contains the segments need to be passed to “gpinitsystem”:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpinitsystem -c gpconfigs\/gpinitsystem_config -h hostfile_gpssh_segonly\n20240229:11:39:11:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking configuration parameters, please wait...\n20240229:11:39:11:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Reading Greenplum configuration file gpconfigs\/gpinitsystem_config\n20240229:11:39:11:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Locale has not been set in gpconfigs\/gpinitsystem_config, will set to default value\n20240229:11:39:11:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:-Coordinator hostname cdw does not match hostname output\n20240229:11:39:11:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking to see if cdw can be resolved on this host\nssh: Could not resolve hostname cdw: Name or service not known\nssh: Could not resolve hostname cdw: Name or service not known\n20240229:11:39:20:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[FATAL]:-Coordinator hostname in configuration file is cdw\n20240229:11:39:20:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[FATAL]:-Operating system command returns rocky9-gp7-master.it.dbi-services.com\n20240229:11:39:20:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[FATAL]:-Unable to resolve cdw on this host\n20240229:11:39:20:001290 gpinitsystem:rocky9-gp7-master:gpadmin-[FATAL]:-Coordinator hostname in gpinitsystem configuration file must be cdw Script Exiting!\n<\/pre><\/div>\n\n\n
It seems the hostname of the coordinator node needs to be “cdw”, so lets add this to the host files on all nodes:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ sudo vi \/etc\/hosts\n[gpadmin@rocky9-gp7-master ~]$ cat \/etc\/hosts\n127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4\n::1         localhost localhost.localdomain localhost6 localhost6.localdomain6\n\n192.168.122.200 rocky9-gp7-master rocky9-gp7-master.it.dbi-services.com cdw cdw.it.dbi-services.com\n192.168.122.201 rocky9-gp7-segment1 rocky9-gp7-segment1.it.dbi-services.com\n192.168.122.202 rocky9-gp7-segment2 rocky9-gp7-segment2.it.dbi-services.com\n<\/pre><\/div>\n\n\n
Running it once more and it looks much better:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpinitsystem -c gpconfigs\/gpinitsystem_config -h hostfile_gpssh_segonly\n20240229:11:45:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking configuration parameters, please wait...\n20240229:11:45:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Reading Greenplum configuration file gpconfigs\/gpinitsystem_config\n20240229:11:45:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Locale has not been set in gpconfigs\/gpinitsystem_config, will set to default value\n20240229:11:45:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:-Coordinator hostname cdw does not match hostname output\n20240229:11:45:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking to see if cdw can be resolved on this host\nThe authenticity of host 'cdw (192.168.122.200)' can't be established.\nED25519 key fingerprint is SHA256:Tdo3AwqH109Mgc30keTbDcusFii8PSft0FXWTUS0Tb0.\nThis host key is known by the following other names\/addresses:\n    ~\/.ssh\/known_hosts:1: rocky9-gp7-segment1\n    ~\/.ssh\/known_hosts:4: rocky9-gp7-segment2\n    ~\/.ssh\/known_hosts:5: rocky9-gp7-master\nAre you sure you want to continue connecting (yes\/no\/[fingerprint])? yes\nWarning: Permanently added 'cdw' (ED25519) to the list of known hosts.\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Can resolve cdw to this host\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-No DATABASE_NAME set, will exit following template1 updates\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-COORDINATOR_MAX_CONNECT not set, will set to default value 250\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking configuration parameters, Completed\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Commencing multi-home checks, please wait...\n..\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Configuring build for standard array\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Commencing multi-home checks, Completed\n20240229:11:45:31:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Building primary segment instance array, please wait...\n....\n20240229:11:45:32:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Building group mirror array type , please wait...\n....\n20240229:11:45:34:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking Coordinator host\n20240229:11:45:34:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking new segment hosts, please wait...\n........\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Checking new segment hosts, Completed\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum Database Creation Parameters\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:---------------------------------------\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator Configuration\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:---------------------------------------\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator hostname       = cdw\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator port           = 5432\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator instance dir   = \/data\/coordinator\/gpseg-1\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator LOCALE         = \n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum segment prefix   = gpseg\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator Database       = \n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator connections    = 250\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator buffers        = 128000kB\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Segment connections        = 750\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Segment buffers            = 128000kB\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Encoding                   = UNICODE\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Postgres param file        = Off\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Initdb to be used          = \/usr\/local\/greenplum-db-7.1.0\/bin\/initdb\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-GP_LIBRARY_PATH is         = \/usr\/local\/greenplum-db-7.1.0\/lib\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-HEAP_CHECKSUM is           = on\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-HBA_HOSTNAMES is           = 0\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Ulimit check               = Passed\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Array host connect type    = Single hostname per node\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator IP address [1]      = ::1\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator IP address [2]      = 192.168.122.200\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator IP address [3]      = fe80::5054:ff:fe5d:fef7\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Standby Coordinator             = Not Configured\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Number of primary segments = 2\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Total Database segments    = 4\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Trusted shell              = ssh\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Number segment hosts       = 2\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Mirror port base           = 7000\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Number of mirror segments  = 2\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Mirroring config           = ON\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Mirroring type             = Group\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:----------------------------------------\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum Primary Segment Configuration\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:----------------------------------------\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment1.it.dbi-services.com     6000    rocky9-gp7-segment1     \/data\/primary\/gpseg0        2\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment1.it.dbi-services.com     6001    rocky9-gp7-segment1     \/data\/primary\/gpseg1        3\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment2.it.dbi-services.com     6000    rocky9-gp7-segment2     \/data\/primary\/gpseg2        4\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment2.it.dbi-services.com     6001    rocky9-gp7-segment2     \/data\/primary\/gpseg3        5\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:---------------------------------------\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum Mirror Segment Configuration\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:---------------------------------------\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment2.it.dbi-services.com     7000    rocky9-gp7-segment2     \/data\/mirror\/gpseg0 6\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment2.it.dbi-services.com     7001    rocky9-gp7-segment2     \/data\/mirror\/gpseg1 7\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment1.it.dbi-services.com     7000    rocky9-gp7-segment1     \/data\/mirror\/gpseg2 8\n20240229:11:45:39:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-rocky9-gp7-segment1.it.dbi-services.com     7001    rocky9-gp7-segment1     \/data\/mirror\/gpseg3 9\n\nContinue with Greenplum creation Yy|Nn (default=N):\n<\/pre><\/div>\n\n\n
Confirming the question leads to this:<\/p>\n\n\n
\n> Y\n20240229:11:48:12:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Building the Coordinator instance database, please wait...\n20240229:11:48:14:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Starting the Coordinator in admin mode\n20240229:11:48:14:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Commencing parallel build of primary segment instances\n20240229:11:48:14:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Spawning parallel processes    batch [1], please wait...\n....\n20240229:11:48:14:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Waiting for parallel processes batch [1], please wait...\n.........\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:------------------------------------------------\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Parallel process exit status\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:------------------------------------------------\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Total processes marked as completed           = 4\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Total processes marked as killed              = 0\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Total processes marked as failed              = 0\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:------------------------------------------------\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Removing back out file\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-No errors generated from parallel processes\n20240229:11:48:23:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Restarting the Greenplum instance in production mode\n20240229:11:48:23:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Starting gpstop with args: -a -l \/home\/gpadmin\/gpAdminLogs -m -d \/data\/coordinator\/gpseg-1\n20240229:11:48:23:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Gathering information and validating the environment...\n20240229:11:48:23:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Obtaining Greenplum Coordinator catalog information\n20240229:11:48:23:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Obtaining Segment details from coordinator...\n20240229:11:48:23:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum Version: 'postgres (Greenplum Database) 7.1.0 build commit:e7c2b1f14bb42a1018ac57d14f4436880e0a0515 Open Source'\n20240229:11:48:23:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Commencing Coordinator instance shutdown with mode='smart'\n20240229:11:48:23:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator segment instance directory=\/data\/coordinator\/gpseg-1\n20240229:11:48:24:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Stopping coordinator segment and waiting for user connections to finish ...\nserver shutting down\n20240229:11:48:25:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Attempting forceful termination of any leftover coordinator process\n20240229:11:48:25:006091 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Terminating processes for segment \/data\/coordinator\/gpseg-1\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Starting gpstart with args: -a -l \/home\/gpadmin\/gpAdminLogs -d \/data\/coordinator\/gpseg-1\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Gathering information and validating the environment...\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 7.1.0 build commit:e7c2b1f14bb42a1018ac57d14f4436880e0a0515 Open Source'\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum Catalog Version: '302307241'\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Starting Coordinator instance in admin mode\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-CoordinatorStart pg_ctl cmd is env GPSESSID=0000000000 GPERA=None $GPHOME\/bin\/pg_ctl -D \/data\/coordinator\/gpseg-1 -l \/data\/coordinator\/gpseg-1\/log\/startup.log -w -t 600 -o " -c gp_role=utility " start\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Obtaining Greenplum Coordinator catalog information\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Obtaining Segment details from coordinator...\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Setting new coordinator era\n20240229:11:48:26:006330 gpstart:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator Started...\nThe authenticity of host 'rocky9-gp7-segment2.it.dbi-services.com (192.168.122.202)' can't be established.\nED25519 key fingerprint is SHA256:Tdo3AwqH109Mgc30keTbDcusFii8PSft0FXWTUS0Tb0.\nThis host key is known by the following other names\/addresses:\n    ~\/.ssh\/known_hosts:1: rocky9-gp7-segment1\n    ~\/.ssh\/known_hosts:4: rocky9-gp7-segment2\n    ~\/.ssh\/known_hosts:5: rocky9-gp7-master\n    ~\/.ssh\/known_hosts:6: cdw\nThe authenticity of host 'rocky9-gp7-segment1.it.dbi-services.com (192.168.122.201)' can't be established.\nED25519 key fingerprint is SHA256:Tdo3AwqH109Mgc30keTbDcusFii8PSft0FXWTUS0Tb0.\nThis host key is known by the following other names\/addresses:\n    ~\/.ssh\/known_hosts:1: rocky9-gp7-segment1\n    ~\/.ssh\/known_hosts:4: rocky9-gp7-segment2\n    ~\/.ssh\/known_hosts:5: rocky9-gp7-master\n    ~\/.ssh\/known_hosts:6: cdw\nAre you sure you want to continue connecting (yes\/no\/[fingerprint])? yes\n\n20240229:11:51:06:006330 gpstart:rocky9-gp7-master:gpadmin-[WARNING]:-One or more hosts are not reachable via SSH.\n20240229:11:51:06:006330 gpstart:rocky9-gp7-master:gpadmin-[WARNING]:-Host rocky9-gp7-segment1.it.dbi-services.com is unreachable\n20240229:11:51:06:006330 gpstart:rocky9-gp7-master:gpadmin-[WARNING]:-Marking segment 2 down because rocky9-gp7-segment1.it.dbi-services.com is unreachable\n20240229:11:51:06:006330 gpstart:rocky9-gp7-master:gpadmin-[CRITICAL]:-gpstart failed. (Reason=''NoneType' object has no attribute 'getSegmentHostName'') exiting...\n20240229:11:51:06:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:\n20240229:11:51:06:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:-Failed to start Greenplum instance; review gpstart output to\n20240229:11:51:06:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:- determine why gpstart failed and reinitialize cluster after resolving\n20240229:11:51:06:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:- issues.  Not all initialization tasks have completed so the cluster\n20240229:11:51:06:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:- should not be used.\n20240229:11:51:06:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:-gpinitsystem will now try to stop the cluster\n20240229:11:51:06:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:\n20240229:11:51:06:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Starting gpstop with args: -a -l \/home\/gpadmin\/gpAdminLogs -i -d \/data\/coordinator\/gpseg-1\n20240229:11:51:06:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Gathering information and validating the environment...\n20240229:11:51:06:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Obtaining Greenplum Coordinator catalog information\n20240229:11:51:06:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Obtaining Segment details from coordinator...\n20240229:11:51:06:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Greenplum Version: 'postgres (Greenplum Database) 7.1.0 build commit:e7c2b1f14bb42a1018ac57d14f4436880e0a0515 Open Source'\n20240229:11:51:06:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Commencing Coordinator instance shutdown with mode='immediate'\n20240229:11:51:06:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Coordinator segment instance directory=\/data\/coordinator\/gpseg-1\n\n20240229:11:51:07:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Attempting forceful termination of any leftover coordinator process\n20240229:11:51:07:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Terminating processes for segment \/data\/coordinator\/gpseg-1\n20240229:11:51:08:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-No standby coordinator host configured\n20240229:11:51:08:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Targeting dbid [2, 3, 4, 5] for shutdown\n20240229:11:51:08:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait...\n20240229:11:51:08:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-0.00% of jobs completed\n20240229:11:51:09:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-100.00% of jobs completed\n20240229:11:51:09:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-----------------------------------------------------\n20240229:11:51:09:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-   Segments stopped successfully      = 4\n20240229:11:51:09:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-   Segments with errors during stop   = 0\n20240229:11:51:09:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-----------------------------------------------------\n20240229:11:51:09:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Successfully shutdown 4 of 4 segment instances \n20240229:11:51:09:006412 gpstop:rocky9-gp7-master:gpadmin-[INFO]:-Database successfully shutdown with no errors reported\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[INFO]:-Successfully shutdown the Greenplum instance\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:-Failed to start Greenplum instance; review gpstart output to\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:- determine why gpstart failed and reinitialize cluster after resolving\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:- issues.  Not all initialization tasks have completed so the cluster\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:- should not be used.\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[WARN]:\n20240229:11:51:09:001611 gpinitsystem:rocky9-gp7-master:gpadmin-[FATAL]: starting new instance failed; Script Exiting!\n\n<\/pre><\/div>\n\n\n
This happens when you do not fully read the documentation<\/a>: “The Greenplum Database host naming convention for the coordinator host is\u00a0cdw<\/code>\u00a0and for the standby coordinator host is\u00a0scdw<\/code>.<\/p>\n\n\n\n
The segment host naming convention is sdwN where sdw is a prefix and N is an integer. For example, segment host names would be\u00a0sdw1<\/code>,\u00a0sdw2<\/code>\u00a0and so on. NIC bonding is recommended for hosts with multiple interfaces, but when the interfaces are not bonded, the convention is to append a dash (-<\/code>) and number to the host name. For example,\u00a0sdw1-1<\/code>\u00a0and\u00a0sdw1-2<\/code>\u00a0are the two interface names for host\u00a0sdw1<\/code>.” <\/p>\n\n\n\n
So, lets fix this (also change the hostname on each node):<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ sudo vi \/etc\/hosts\n[gpadmin@rocky9-gp7-master ~]$ cat \/etc\/hosts\n127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4\n::1         localhost localhost.localdomain localhost6 localhost6.localdomain6\n\n192.168.122.200 cdw cdw.it.dbi-services.com\n192.168.122.201 sdw1 sdw1.it.dbi-services.com\n192.168.122.202 sdw2 sdw2.it.dbi-services.com\n\n[gpadmin@rocky9-gp7-master ~]$ cat hostfile_gpssh_segonly \nsdw1\nsdw2\n\n[gpadmin@rocky9-gp7-master ~]$ cat hostfile_exkeys \ncdw\nsdw1\nsdw2\n<\/pre><\/div>\n\n\n
Before initializing the system again, lets cleanup what was already created:<\/p>\n\n\n
\n[gpadmin@rocky9-gp7-master ~]$ gpssh -f hostfile_gpssh_segonly -e "rm -rf \/data\/primary\/*; rm -rf \/data\/mirror\/*; rm -rf \/data\/coordinator\/*"\n[sdw2] rm -rf \/data\/primary\/*; rm -rf \/data\/mirror\/*; rm -rf \/data\/coordinator\/*\n[sdw1] rm -rf \/data\/primary\/*; rm -rf \/data\/mirror\/*; rm -rf \/data\/coordinator\/*\n[gpadmin@rocky9-gp7-master ~]$ rm -rf \/data\/coordinator\/*\n<\/pre><\/div>\n\n\n
Next try:<\/p>\n\n\n
\n[gpadmin@cdw ~]$ gpinitsystem -c gpconfigs\/gpinitsystem_config -h hostfile_gpssh_segonly\n20240229:12:51:03:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Checking configuration parameters, please wait...\n20240229:12:51:03:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Reading Greenplum configuration file gpconfigs\/gpinitsystem_config\n20240229:12:51:03:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Locale has not been set in gpconfigs\/gpinitsystem_config, will set to default value\n20240229:12:51:03:013410 gpinitsystem:cdw:gpadmin-[INFO]:-No DATABASE_NAME set, will exit following template1 updates\n20240229:12:51:03:013410 gpinitsystem:cdw:gpadmin-[INFO]:-COORDINATOR_MAX_CONNECT not set, will set to default value 250\n20240229:12:51:03:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Checking configuration parameters, Completed\n20240229:12:51:03:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Commencing multi-home checks, please wait...\n..\n20240229:12:51:04:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Configuring build for standard array\n20240229:12:51:04:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Commencing multi-home checks, Completed\n20240229:12:51:04:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Building primary segment instance array, please wait...\n..\n20240229:12:51:04:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Building group mirror array type , please wait...\n..\n20240229:12:51:05:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Checking Coordinator host\n20240229:12:51:05:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Checking new segment hosts, please wait...\n....\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Checking new segment hosts, Completed\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Greenplum Database Creation Parameters\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:---------------------------------------\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator Configuration\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:---------------------------------------\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator hostname       = cdw\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator port           = 5432\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator instance dir   = \/data\/coordinator\/gpseg-1\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator LOCALE         = \n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Greenplum segment prefix   = gpseg\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator Database       = \n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator connections    = 250\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator buffers        = 128000kB\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Segment connections        = 750\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Segment buffers            = 128000kB\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Encoding                   = UNICODE\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Postgres param file        = Off\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Initdb to be used          = \/usr\/local\/greenplum-db-7.1.0\/bin\/initdb\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-GP_LIBRARY_PATH is         = \/usr\/local\/greenplum-db-7.1.0\/lib\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-HEAP_CHECKSUM is           = on\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-HBA_HOSTNAMES is           = 0\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Ulimit check               = Passed\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Array host connect type    = Single hostname per node\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator IP address [1]      = ::1\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator IP address [2]      = 192.168.122.200\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Coordinator IP address [3]      = fe80::5054:ff:fe5d:fef7\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Standby Coordinator             = Not Configured\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Number of primary segments = 1\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Total Database segments    = 2\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Trusted shell              = ssh\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Number segment hosts       = 2\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Mirror port base           = 7000\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Number of mirror segments  = 1\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Mirroring config           = ON\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Mirroring type             = Group\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:----------------------------------------\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Greenplum Primary Segment Configuration\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:----------------------------------------\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-sdw1  6000    sdw1    \/data\/primary\/gpseg0   2\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-sdw2  6000    sdw2    \/data\/primary\/gpseg1   3\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:---------------------------------------\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Greenplum Mirror Segment Configuration\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:---------------------------------------\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-sdw2  7000    sdw2    \/data\/mirror\/gpseg0    4\n20240229:12:51:08:013410 gpinitsystem:cdw:gpadmin-[INFO]:-sdw1  7000    sdw1    \/data\/mirror\/gpseg1    5\n\nContinue with Greenplum creation Yy|Nn (default=N):\n> y\n20240229:12:51:12:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Building the Coordinator instance database, please wait...\n20240229:12:51:13:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Starting the Coordinator in admin mode\n20240229:12:51:13:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Commencing parallel build of primary segment instances\n20240229:12:51:13:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Spawning parallel processes    batch [1], please wait...\n..\n20240229:12:51:13:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Waiting for parallel processes batch [1], please wait...\n.......\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:------------------------------------------------\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Parallel process exit status\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:------------------------------------------------\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Total processes marked as completed           = 2\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Total processes marked as killed              = 0\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Total processes marked as failed              = 0\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:------------------------------------------------\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Removing back out file\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:-No errors generated from parallel processes\n20240229:12:51:20:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Restarting the Greenplum instance in production mode\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Starting gpstop with args: -a -l \/home\/gpadmin\/gpAdminLogs -m -d \/data\/coordinator\/gpseg-1\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Gathering information and validating the environment...\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Obtaining Greenplum Coordinator catalog information\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Obtaining Segment details from coordinator...\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Greenplum Version: 'postgres (Greenplum Database) 7.1.0 build commit:e7c2b1f14bb42a1018ac57d14f4436880e0a0515 Open Source'\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Commencing Coordinator instance shutdown with mode='smart'\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Coordinator segment instance directory=\/data\/coordinator\/gpseg-1\n20240229:12:51:20:016290 gpstop:cdw:gpadmin-[INFO]:-Stopping coordinator segment and waiting for user connections to finish ...\nserver shutting down\n20240229:12:51:21:016290 gpstop:cdw:gpadmin-[INFO]:-Attempting forceful termination of any leftover coordinator process\n20240229:12:51:21:016290 gpstop:cdw:gpadmin-[INFO]:-Terminating processes for segment \/data\/coordinator\/gpseg-1\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Starting gpstart with args: -a -l \/home\/gpadmin\/gpAdminLogs -d \/data\/coordinator\/gpseg-1\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Gathering information and validating the environment...\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 7.1.0 build commit:e7c2b1f14bb42a1018ac57d14f4436880e0a0515 Open Source'\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Greenplum Catalog Version: '302307241'\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Starting Coordinator instance in admin mode\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-CoordinatorStart pg_ctl cmd is env GPSESSID=0000000000 GPERA=None $GPHOME\/bin\/pg_ctl -D \/data\/coordinator\/gpseg-1 -l \/data\/coordinator\/gpseg-1\/log\/startup.log -w -t 600 -o " -c gp_role=utility " start\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Obtaining Greenplum Coordinator catalog information\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Obtaining Segment details from coordinator...\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Setting new coordinator era\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Coordinator Started...\n20240229:12:51:23:016530 gpstart:cdw:gpadmin-[INFO]:-Shutting down coordinator\n20240229:12:51:24:016530 gpstart:cdw:gpadmin-[INFO]:-Commencing parallel segment instance startup, please wait...\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-Process results...\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-----------------------------------------------------\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-   Successful segment starts                                            = 2\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-   Failed segment starts                                                = 0\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-   Skipped segment starts (segments are marked down in configuration)   = 0\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-----------------------------------------------------\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-Successfully started 2 of 2 segment instances \n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-----------------------------------------------------\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-Starting Coordinator instance cdw directory \/data\/coordinator\/gpseg-1 \n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-CoordinatorStart pg_ctl cmd is env GPSESSID=0000000000 GPERA=b37f5ee82ead4186_240229125123 $GPHOME\/bin\/pg_ctl -D \/data\/coordinator\/gpseg-1 -l \/data\/coordinator\/gpseg-1\/log\/startup.log -w -t 600 -o " -c gp_role=dispatch " start\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-Command pg_ctl reports Coordinator cdw instance active\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-Connecting to db template1 on host localhost\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-No standby coordinator configured.  skipping...\n20240229:12:51:25:016530 gpstart:cdw:gpadmin-[INFO]:-Database successfully started\n20240229:12:51:25:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Completed restart of Greenplum instance in production mode\n20240229:12:51:25:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Creating core GPDB extensions\n20240229:12:51:25:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Importing system collations\n20240229:12:51:27:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Commencing parallel build of mirror segment instances\n20240229:12:51:27:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Spawning parallel processes    batch [1], please wait...\n..\n20240229:12:51:27:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Waiting for parallel processes batch [1], please wait...\n......\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:------------------------------------------------\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Parallel process exit status\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:------------------------------------------------\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Total processes marked as completed           = 2\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Total processes marked as killed              = 0\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Total processes marked as failed              = 0\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:------------------------------------------------\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Scanning utility log file for any warning messages\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[WARN]:-*******************************************************\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[WARN]:-Scan of log file indicates that some warnings or errors\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[WARN]:-were generated during the array creation\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Please review contents of log file\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-\/home\/gpadmin\/gpAdminLogs\/gpinitsystem_20240229.log\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-To determine level of criticality\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-These messages could be from a previous run of the utility\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-that was called today!\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[WARN]:-*******************************************************\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Greenplum Database instance successfully created\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-------------------------------------------------------\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-To complete the environment configuration, please \n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-update gpadmin .bashrc file with the following\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-1. Ensure that the greenplum_path.sh file is sourced\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-2. Add "export COORDINATOR_DATA_DIRECTORY=\/data\/coordinator\/gpseg-1"\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-   to access the Greenplum scripts for this instance:\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-   or, use -d \/data\/coordinator\/gpseg-1 option for the Greenplum scripts\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-   Example gpstate -d \/data\/coordinator\/gpseg-1\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Script log file = \/home\/gpadmin\/gpAdminLogs\/gpinitsystem_20240229.log\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-To remove instance, run gpdeletesystem utility\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-To initialize a Standby Coordinator Segment for this Greenplum instance\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Review options for gpinitstandby\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-------------------------------------------------------\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-The Coordinator \/data\/coordinator\/gpseg-1\/pg_hba.conf post gpinitsystem\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-has been configured to allow all hosts within this new\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-array to intercommunicate. Any hosts external to this\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-new array must be explicitly added to this file\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-Refer to the Greenplum Admin support guide which is\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-located in the \/usr\/local\/greenplum-db-7.1.0\/docs directory\n20240229:12:51:34:013410 gpinitsystem:cdw:gpadmin-[INFO]:-------------------------------------------------------\n<\/pre><\/div>\n\n\n
All fine. The last step from the documentation is to set the time zone with “gpconfig”. To list the current time zone which is used by the system:<\/p>\n\n\n
\n[gpadmin@cdw ~]$ gpconfig -s TimeZone\nValues on all segments are consistent\nGUC              : TimeZone\nCoordinator value: Europe\/Zurich\nSegment     value: Europe\/Zurich\n<\/pre><\/div>\n\n\n
To set the time zone:<\/p>\n\n\n
\n[gpadmin@cdw ~]$ gpconfig -c TimeZone -v 'Europe\/Zurich'\nEnvironment Variable COORDINATOR_DATA_DIRECTORY not set!\n[gpadmin@cdw ~]$ export COORDINATOR_DATA_DIRECTORY=\/data\/coordinator\/gpseg-1\/\n[gpadmin@cdw ~]$ gpconfig -c TimeZone -v 'Europe\/Zurich'\n20240229:13:01:03:017941 gpconfig:cdw:gpadmin-[INFO]:-completed successfully with parameters '-c TimeZone -v Europe\/Zurich'\n<\/pre><\/div>\n\n\n
That’s it for the scope of this post. In the next post we’ll look in more detail what got created and how the PostgreSQL instances interact with each other.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the last post we’ve configured the operating system for Greenplum and completed the installation. In this post we’ll create the so called “Data Storage Areas” (which is just a mount point or directory) and initialize the cluster. All the work is performed on the “Coordinator Host” and “gpssh” is used to perform the work […]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[3276,77],"type_dbi":[],"class_list":["post-31478","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-greenplum","tag-postgresql"],"acf":[],"yoast_head":"\nGetting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster\" \/>\n<meta property=\"og:description\" content=\"In the last post we’ve configured the operating system for Greenplum and completed the installation. In this post we’ll create the so called “Data Storage Areas” (which is just a mount point or directory) and initialize the cluster. All the work is performed on the “Coordinator Host” and “gpssh” is used to perform the work […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2024-02-29T12:11:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-02-29T12:11:07+00:00\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster\",\"datePublished\":\"2024-02-29T12:11:05+00:00\",\"dateModified\":\"2024-02-29T12:11:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/\"},\"wordCount\":713,\"commentCount\":0,\"keywords\":[\"Greenplum\",\"PostgreSQL\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/\",\"name\":\"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2024-02-29T12:11:05+00:00\",\"dateModified\":\"2024-02-29T12:11:07+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\/\/x.com\/westermanndanie\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/","og_locale":"en_US","og_type":"article","og_title":"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster","og_description":"In the last post we’ve configured the operating system for Greenplum and completed the installation. In this post we’ll create the so called “Data Storage Areas” (which is just a mount point or directory) and initialize the cluster. All the work is performed on the “Coordinator Host” and “gpssh” is used to perform the work […]","og_url":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/","og_site_name":"dbi Blog","article_published_time":"2024-02-29T12:11:05+00:00","article_modified_time":"2024-02-29T12:11:07+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster","datePublished":"2024-02-29T12:11:05+00:00","dateModified":"2024-02-29T12:11:07+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/"},"wordCount":713,"commentCount":0,"keywords":["Greenplum","PostgreSQL"],"articleSection":["Database Administration & Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/","url":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/","name":"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2024-02-29T12:11:05+00:00","dateModified":"2024-02-29T12:11:07+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-greenplum-2-initializing-and-bringing-up-the-cluster\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Getting started with Greenplum \u2013 2 \u2013 Initializing and bringing up the cluster"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/31478","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=31478"}],"version-history":[{"count":15,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/31478\/revisions"}],"predecessor-version":[{"id":31519,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/31478\/revisions\/31519"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=31478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=31478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=31478"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=31478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}