Intro to Greenplum

Greenplum Database stores and processes large amounts of data by distributing the load across several servers or hosts
A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image. 
The master is the entry point to the Greenplum Database system. 
It is the database instance to which users connect and submit SQL statements. 
The master coordinates the workload across the other database instances in the system, called segments, which handle data processing and storage. 
The segments communicate with each other and the master over the interconnect the networking layer of Greenplum Database.

Greenplum Database is a software-only solution; the hardware and database software are not coupled. 
Greenplum Database runs on a variety of commodity server platforms from Greenplum-certified hardware vendors. 
Performance depends on the hardware on which it is installed. 
Because the database is distributed across multiple machines in a Greenplum Database system, proper selection and configuration of hardware is vital to achieving the best possible performance.

With the above said, Before deep diving into each major components of a Greenplum Database system and the hardware considerations and concepts associated with each components we are in need to have a clear picture of few basic things listed below
  1. Disks
  2. RAID
  3. XOR Operation
  4. Basic Networking
  5. LAN
  6. Linux - Basic

After going thru all above said hope now your equipped with enough knowledge to understand the technical terms mentioned in up-coming posts on below listed major components of a Greenplum Database system and the hardware considerations and concepts associated with each component: 
  1. The Greenplum Master 
  2. The Segments
  3. The Interconnect

Additionally, a system may have optional ETL Hosts for Data Loading and the Greenplum Performance Monitor for monitoring query workload and performance.

Comments

Post a Comment

Popular posts from this blog

GP - Kerberos errors and resolutions

Issue:1. Ticket granting has expired with the error message, ERROR: psql: GSSAPI continuation error: Unspecified GSS failure. The Minor code may also display the error message, GSSAPI continuation error: Ticket expired. Solution: Create a new ticket on the Master server using the following command: kinit -k -t /home/gpadmin/gpdb-kerberos.keytab db_user Note: -t is the keytab file and db_user is the user. Issue:2. The library required to run the kinit command does not exist in the LD_LIBRARY_PATH  set in the Greenplum binaries, producing the following error message: ERROR: kinit: relocation error: kinit: symbol krb5_get_init_creds_opt_set_fast_ccache_name, version krb5_3_MIT not defined in file libkrb5.so.3 with link time reference Solution: Unset the LD_LIBRARY_PATH. IMPORTANT NOTE: The above fix will cause the following error when you try to run Postgres commands:  ERROR: psql: error while loading shared libraries: libpq.so.5: cannot open shared object ...
Read more

How to set Optimizer at database level in greenplum

How can I turn ON optimizer at Database level? You can set the optimier ON at database level using below command; ALTER DATABASE databasename SET OPTIMIZER = ON; Once this is done, kindly do reconnect to Database to see the change. How do I check if optimizer is set (ON/OFF) in a given database? You can use the show command as below to check psql -d databasename -c 'show optimizer'
Read more

GP - SQL Joins

Image
Available Join Types? Row Elimination Minimize Data Movement Join Implementation Seen in Query Plans Join Types: Inner Join Resulting data set is obtained from joining two tables on a common column Each row in left table is compared with each row in right table Matching rows will be present in result set Most commonly used Also know has Simple Join or EQUI-Join Left Outer Join Returns all rows from the left table even if there is no matching rows in right table. Will also get the matching rows Rows that are not matched in the right table will not be included in the result set Right Outer Join This is similar to left outer join, just need to flip the join Full Outer Join Will return all rows from both the tables where there is a match We will receive a NULL for rows which don’t match Cross Join Which is also called has Cartesian products Result set will have all rows on the left table paired with all rows on the right table Exam...
Read more