table of contents - pivotal gpcc docs · pivotal greenplum command center is a management tool for...

110
1 3 4 7 8 10 11 12 14 16 17 19 22 23 24 26 28 29 30 31 33 34 36 37 38 39 41 42 43 44 45 46 47 49 51 53 58 60 61 63 65 66 68 69 71 72 73 74 Table of Contents Table of Contents Pivotal Greenplum Command Center Documentation About Pivotal Greenplum Command Center Installing the Greenplum Command Center Software Downloading and Running the Greenplum Command Center Installer About the Command Center Installation Setting the Greenplum Command Center Environment Creating the gpperfmon Database Upgrading Greenplum Command Center Uninstalling Greenplum Command Center Running Greenplum Command Center 2.x in Parallel With 3.x Creating Greenplum Command Center Console Instances Connecting to the Greenplum Command Center Console Greenplum Command Center User Guide Dashboard Query Monitor Host Metrics Cluster Metrics Monitoring Multiple Greenplum Database Clusters History System Segment Status Storage Status Admin Permission Levels for GPCC Access Authentication Administering Greenplum Command Center Starting and Stopping Greenplum Command Center Administering Command Center Agents Administering the Command Center Database Administering the Web Server Configuring Greenplum Command Center Enabling Multi-Cluster Support Securing a Greenplum Command Center Console Instance Configuring Authentication for the Command Center Console Enabling Authentication with Kerberos Securing the gpmon Database User Utility Reference gpperfmon_install gpcmdr Configuration File Reference Command Center Agent Parameters Command Center Console Parameters Setup Configuration File Greenplum Database Server Configuration Parameters Command Center Database Reference database_* emcconnect_history © Copyright Pivotal Software Inc, 2013-2016 1 3.1.1

Upload: others

Post on 09-Aug-2020

21 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

1347810111214161719222324262829303133343637383941424344454647495153586061636566686971727374

TableofContents

TableofContentsPivotalGreenplumCommandCenterDocumentationAboutPivotalGreenplumCommandCenterInstallingtheGreenplumCommandCenterSoftwareDownloadingandRunningtheGreenplumCommandCenterInstallerAbouttheCommandCenterInstallationSettingtheGreenplumCommandCenterEnvironmentCreatingthegpperfmonDatabaseUpgradingGreenplumCommandCenterUninstallingGreenplumCommandCenterRunningGreenplumCommandCenter2.xinParallelWith3.xCreatingGreenplumCommandCenterConsoleInstancesConnectingtotheGreenplumCommandCenterConsoleGreenplumCommandCenterUserGuideDashboardQueryMonitorHostMetricsClusterMetricsMonitoringMultipleGreenplumDatabaseClustersHistorySystemSegmentStatusStorageStatusAdminPermissionLevelsforGPCCAccessAuthenticationAdministeringGreenplumCommandCenterStartingandStoppingGreenplumCommandCenterAdministeringCommandCenterAgentsAdministeringtheCommandCenterDatabaseAdministeringtheWebServerConfiguringGreenplumCommandCenterEnablingMulti-ClusterSupportSecuringaGreenplumCommandCenterConsoleInstanceConfiguringAuthenticationfortheCommandCenterConsoleEnablingAuthenticationwithKerberosSecuringthegpmonDatabaseUserUtilityReferencegpperfmon_installgpcmdrConfigurationFileReferenceCommandCenterAgentParametersCommandCenterConsoleParametersSetupConfigurationFileGreenplumDatabaseServerConfigurationParametersCommandCenterDatabaseReferencedatabase_*emcconnect_history

©CopyrightPivotalSoftwareInc,2013-2016 1 3.1.1

Page 2: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

7576808182869799101102103104105106109110

diskspace_*filerep_*health_*interface_stats_*iterators_*IteratorMetricslog_alert_*queries_*segment_*socket_stats_*system_*tcp_stats_*udp_stats_*iterators_*_rollupdynamic_memory_infomemory_info

©CopyrightPivotalSoftwareInc,2013-2016 2 3.1.1

Page 3: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

PivotalGreenplumCommandCenterDocumentationDocumentationforPivotalGreenplumCommandCenter.

AboutGreenplumCommandCenterPivotalGreenplumCommandCenterisamanagementtoolfortheGreenplumBigDataPlatform.ThissectionintroduceskeyconceptsaboutGreenplumCommandCenteranditscomponents.

InstallingtheGreenplumCommandCenterSoftwareDownloadingandinstallingtheGreenplumCommandCentersoftwareinyourGreenplumclusterandone-timetasks.ThissectionalsoprovidesinstructionsforupgradingCommandCentertoanewreleaseandmigratingCommandCenterinstances.

CreatingGreenplumCommandCenterConsoleInstancesCreatingaCommandCenterConsoleinstancetomanageaGreenplumcluster.

UsingtheGreenplumCommandCenterWebInterfaceUsingtheGreenplumCommandCenterwebuserinterfacetomonitorandmanageaGreenplumcluster.

AdministeringGreenplumCommandCenterSystemadministrationinformationfortheGreenplumCommandCentercomponents.

UtilityReferenceReferenceinformationforthetwoGreenplumCommandCenterutilityprograms:the gpperfmon_install utilitythatenablesthedatacollectionagentsandthe gpcmdr utilitythatsetsupandmanagesthewebapplication.

ConfigurationFileReferenceReferencesforGreenplumCommandCenterconfigurationfiles.

CommandCenterDatabaseReferenceReferencesfortheGreenplumCommandCenter gpperfmon databasetables.

©CopyrightPivotalSoftwareInc,2013-2016 3 3.1.1

Page 4: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AboutPivotalGreenplumCommandCenterPivotalGreenplumCommandCenterisamanagementtoolfortheGreenplumBigDataPlatform.ThissectionintroduceskeyconceptsaboutGreenplumCommandCenteranditscomponents.

IntroductionGreenplumCommandCentermonitorssystemperformancemetrics,analyzessystemhealth,andallowsadministratorstoperformsomemanagementtasksinaGreenplumenvironment.TheGreenplumCommandCenterConsoleisaninteractivegraphicalwebapplicationthatisinstalledonawebserver,usuallyonthemasterhost.UsersviewandinteractwiththecollectedGreenplumsystemdatathroughthisapplication.

GreenplumCommandCenteriscomprisedofdatacollectionagentsthatrunonthemasterhostandeachsegmenthost.TheagentscollectdataaboutqueriesandsystemutilizationandupdatetheGreenplummasterhostatregularintervals.GreenplumCommandCenterstoresitsdataandmetricsinadedicatedGreenplumdatabase(theCommandCenterdatabase,gpperfmon)whoseinformationisdistributedamongthemasterhostandsegmenthostslikeanyotherGreenplumDatabase.YoucanaccessthedatastoredintheCommandCenterdatabasethroughtheGreenplumCommandCenterConsoleandthroughSQLqueries.

Note:CommandCenterrequiresGreenplumDatabasetooperatebecauseCommandCenterstoresitsinformationinaGreenplumdatabase.

SupportedGreenplumPlatformsGreenplumCommandCenteriscurrentlycertifiedfortheGreenplumDataComputingAppliance(DCA)andGreenplumDatabasesoftware-onlyenvironments.CommandCentermonitorsthefollowingforeachenvironment:

GreenplumDataComputingAlliance:

GreenplumDatabaseModule

GreenplumDatabase(software-onlyenvironments):

GreenplumDatabase

SeetheReleaseNotesforyourGreenplumCommandCenterreleaseforinformationaboutthesupportedsoftwareandhardwareversions.

ArchitectureThefollowingfigureillustratestheGreenplumCommandCenterarchitecture.

©CopyrightPivotalSoftwareInc,2013-2016 4 3.1.1

Page 5: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

GreenplumDataCollectionAgentsGreenplumdatacollectionagentsrunonGreenplumsegmenthoststocollectthequeryandsystemstatisticstobedisplayedintheCommandCenter.TheagentsareinstalledwiththeGreenplumDatabasedistributionbutarenotenableduntilyoucreatetheGreenplumCommandCenterdatabase(gpperfmon)andstartthem.Theagentsmayalsobeenabledordisabledbysettingthe gp_enable_gpperfmon serverconfigurationparameter.Whenthisparameterisenabled,thedatacollectionagentsrunonallGreenplumhosts(masterandsegments),andstartandstopalongwithGreenplumDatabaseserverprocesses.

Themasteragentpollsallsegmentagentsforsystemmetricsandotherdataataconfigurableinterval(calledthequantum).Themasteragentamassesthedatafromallsegments,storesitinflatfiles,andperiodicallycommitsthedatainthefilestotheGreenplumCommandCenterdatabase.

GreenplumCommandCenterDatabaseTheGreenplumCommandCenterdatabase(gpperfmon)isadatabasewithinyourGreenplumsystemdedicatedtostoringandservingsystemdata.YourGreenplumDatabaseinstallationincludesthe gpperfmon_install utilitytoinstalltheCommandCenterdatabaseandoptionallystartthedatacollectionagents.

WhenthisdocumentreferstotheCommandCenterdatabase,itisreferringtothedatabasenamedgpperfmon.

GreenplumadministratorscanconnecttotheCommandCenterdatabaseusingclientprogramssuchaspsqlorapplicationprogramminginterfaces(APIs)suchasJDBC(JavaDatabaseConnectivity)andODBC(OpenDatabaseConnectivity).AdministratorscanalsousetheGreenplumCommandCenterConsoletoviewreportsoncurrentandhistoricalperformanceandperformothermanagementtasks.

TheCommandCenterdatabaseconsistsofthreesetsoftables;nowtablesstoredataoncurrentsystemmetricssuchasactivequeries,historytablesstoredataonhistoricalmetrics,andtailtablesarefordataintransition.Tailtablesareforinternaluseonlyandshouldnotbequeriedbyusers.Thenowandtaildataarestoredastextfilesonthemasterhostfilesystem,andtheCommandCenterdatabaseaccessesthemviaexternaltables.ThehistorytablesareregulardatabasetablesstoredwithintheCommandCenter(gpperfmon)database.SeeCommandCenterDatabaseReferencefortheschemadefinitionsofthesetables.

GreenplumCommandCenterConsoleGreenplumCommandCenterprovidesabrowser-nativeHTML5graphicalconsoleforviewingGreenplumDatabasesystemmetricsandperformingcertaindatabaseadministrativetasks.Thisbrowser-basedapplicationprovidesthefollowingfunctionality:

Interactiveoverviewofrealtimesystemmetrics

Detailedrealtimestatisticsfortheclusterandbyserver

QueryMonitorviewlistsqueriesexecutingandwaitingtoexecute

Fourpermissionlevelstoallowuserstovieworcanceltheirownorothers’queries,andtoviewormanageadministrativeinformation

ClusterMetricsviewshowssynchronizedchartsofhistoricalsystemmetrics

Historyviewlistscompletedqueriesandsystemmetricsplottedoveraselectedtimeperiod

Selectaquerytoviewquerytextandexplainplan

SegmentStatusviewwithsummariesanddetailsbysegment

StorageStatusviewwithsummariesanddetailsbysegmentdatadirectory

Admin>Permissionsviewtoseeormanagepermissionlevels

Admin>Authenticationviewtoseeoreditthe pg_hba.con host-basedauthenticationconfigurationfile

IfyouhavemultipleGreenplumenvironments,youcancreateseparateCommandCenterinstancesforthem.Eachseparateconsoleinstanceoperatesonauniqueportandhasitsownuniqueconfigurationoptions.Formoreinformation,seeCreatingGreenplumCommandCenterConsoleInstances.

GreenplumCommandCenterWebServiceTheGreenplumCommandCenterConsolequeriestheCommandCenterdatabasethroughawebserviceframeworkcomposedofalightweightgo-basedwebserver.

Theconsolesetuputility, gpcmdr ,setsupthewebserverandwebservice,promptingyouforbasicconfigurationinformationonthedesiredportandSSLoptions.Undernormalconditions,thewebserverandwebserviceAPIrequireminimalmaintenanceandadministration,asdescribedinWebServer

©CopyrightPivotalSoftwareInc,2013-2016 5 3.1.1

Page 6: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

Administration.

©CopyrightPivotalSoftwareInc,2013-2016 6 3.1.1

Page 7: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

InstallingtheGreenplumCommandCenterSoftware

InstallationNotesGreenplumCommandCentermaybeinstalledonaDellEMCDataComputingAppliance(DCA)orinaGreenplumDatabasesoftwareenvironment.

CommandCenteriscompatiblewiththeDataComputingAppliance(DCA),versions1.2.x,2.x,and3.x.VisitPivotalNetwork todownloadaninstallerforthemostrecent3.xversionforyourDCA.SeetheDellEMCDCAdocumentationforinformationaboutinstallingthesoftwareonyourappliance.

TheGreenplumCommandCentersoftwareistypicallyinstalledontheGreenplumDatabasemasterhost.Installingonthemasterhostprovidesthebestperformanceandsecurity,sincetheCommandCenterConsoledatabaserequestsarenotpassedoverthenetwork.

IfyouareinstallingtheCommandCenterConsoleonaremotesystem(thatis,notthesamesystemonwhichyouinstalledGreenplumDatabase),youmustfirstinstalltheGreenplumDatabasebinarysoftwarefilesontheremotesystem.Notethatyoudonotneedtoinitializethedatabaseontheremotesystem.SeetheGreenplumDatabaseInstallationGuideforhelpinstallingtheGreenplumDatabasesoftware.

IfyouwanttousefeaturesofGreenplumCommandCenter2.xthatarenotavailableinthe3.xrelease,seeRunningGreenplumCommandCenter2.xinParallelWith3.x.

Thissectioncontainsthefollowingtopics:

DownloadingandRunningtheGreenplumCommandCenterInstaller

SettingtheGreenplumCommandCenterEnvironment

CreatingthegpperfmonDatabase

UpgradingtheGreenplumCommandCenterSoftware

UninstallingGreenplumCommandCenter

RunningGreenplumCommandCenter2.xinParallelWith3.x

TheGreenplumWorkloadManagerinstallerisincludedintheGreenplumCommandCenterinstaller.InstallWorkloadManagerusingitsbundledinstaller.SeetheGreenplumWorkloadManagerdocumentation forinstructionstoruntheGreenplumWorkloadManagerinstaller.

©CopyrightPivotalSoftwareInc,2013-2016 7 3.1.1

Page 8: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

DownloadingandRunningtheGreenplumCommandCenterInstaller

DownloadandRuntheInstallerImportant:The gpadmin userownsandexecutestheGreenplumCommandCentersoftware,whichisinstalledinthe /usr/local directorybydefault.Beforeyoubegininstalling,ensurethatthe gpadmin userhaswritepermissioninthedirectorywhereyouwillinstallthesoftware.Besuretopreparethestandbymasterhostinthesameway.Alternatively,youcanruntheinstalleras root and,afterinstallation,changetheowneroftheinstallationdirectoryanditscontentsto gpadmin .

Followthesestepsas gpadmin todownloadandinstalltheGreenplumCommandCentersoftware.

1. DownloadtheGreenplumCommandCenterinstallerfilefromtheGreenplumDatabasesectionofPivotalNetwork .InstallerfilesareavailableforLinux64-bitplatforms.

2. Unziptheinstallerfile.

$unzipgreenplum-cc-web-3.X.X-LINUX-x86_64.zip

3. Launchtheinstallerwith bash :

$/bin/bashgreenplum-cc-web-3.X.X-LINUX.bin

4. Readthroughthelicenseagreement.Whenyoureachthebottom,type yes toacceptthelicenseagreement.

5. Theinstallerpromptsyoutoprovideaninstallationpath.PressEntertoacceptthedefaultinstallationpath( /usr/local/greenplum-cc-web-X.X.X ),orenteranabsolutepathtoanotherinstalllocation.Youmusthavewritepermissioninthelocationyouspecify.

6. Theinstallerthenasksifyouwanttoinstallonthestandbymaster.Enter no ifyoudonotwanttoinstallthesoftwaretothestandbymasterhostnow.Youcaninstallthesoftwaretothestandbymasterlaterusingthe gpccinstall utility.SeeInstallGreenplumCommandCenterSoftwareonAdditionalHosts.Enter yes toinstalltheGreenplumCommandCentersoftwareonthestandbymasterhost,thenenterthenameofthehost.

7. Theinstallercompleteswithasummaryoftheactionsthatwereperformed.

Note:Ifyouhaveperformedthepreviousstepsasanyuserotherthan gpadmin ,youneedtochangeownershipandpermissionsoftheinstallationdirectorybeforeyoucontinue.

Changetheownershipoftheinstallationdirectory:

#chown-Rgpadmin:gpadmingreenplum-cc-web-X.X.X

Changethepermissionsoftheinstallationdirectory:

#chmod-R755greenplum-cc-web-X.X.X

InstallGreenplumCommandCenterSoftwareonAdditionalHostsFollowthestepsinthissectiontoinstalltheGreenplumCommandCentersoftwareonthestandbymasterhostoronotherhostswhereyouwanttorunGreenplumCommandCenterconsoleinstances.

Runthe gpccinstall utilityasthe gpadmin useronthehostwhereyouinstalledtheGreenplumCommandCentersoftware.

1. Createatextfilecontainingthenamesofthestandbymasterhostandotherhostswherethesoftwareistobeinstalled,onenameperline.Donotincludethenameofthehostwhereyourantheinstaller.HostnamesmustberesolvableinDNS.Forexample:

smdwgpspare

©CopyrightPivotalSoftwareInc,2013-2016 8 3.1.1

Page 9: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

2. SourcetheGreenplumDatabaseandCommandCenterpathfiles.

$source/usr/local/greenplum-db/greenplum_path.sh$source/usr/local/greenplum-cc-web/gpcc_path.sh

3. As gpadmin ,runthe gpccinstall utilitytoinstallCommandCenteronallhostslistedinthehostfileyoucreated.

$gpccinstall-fhostfilename

where hostfilename isthenameofthehostfileyoucreated.

©CopyrightPivotalSoftwareInc,2013-2016 9 3.1.1

Page 10: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AbouttheCommandCenterInstallationTheinstallationandsetupprocedurescreateasoftwareinstallationdirectoryandadirectorycontainingfilesandfolderstosupporteachGreenplumCommandCenterConsoleinstance.

SoftwareInstallationDirectoryThefollowingfilesandfirst-levelsubdirectoriesarecopiedintotheinstallationfolderthatyouspecifiedwhenyouinstalledGreenplumCommandCenterConsole.Thislocationisreferredtoas $GPPERFMONHOME .

gpcc_path.sh –filecontainingenvironmentvariablesforCommandCenter

bin –programfilesforGreenplumCommandCenter

etc –contains openssl.cnf file

gpcc-wlm-<version>-<platform>.bin –installerforGreenplumWorkloadManager

instances –containsasubdirectoryofresourcesforeachGreenplumDatabaseinstancemonitoredbytheconsole

lib –libraryfilesforGreenplumCommandCenter

open_source_licenses_GPCC.txt –licensesforopensourcecomponentsusedbyGreenplumCommandCenter

www –webserveranduserinterfacefiles

InstancesDirectoryThe $GPPERFMONHOME/instances directorycontainssubdirectoriesnamedforeachinstancecreatedduringconsolesetup.The conf subdirectorycontainsconfigurationfilesthatyoucanedit.Otherfilesandfoldersareusedbythewebservicesfortheinstance,andshouldnotbemodifiedordeleted.

Eachsubdirectorycontainsthefollowingfilesandfirst-levelsubdirectories:

conf –multi-clusterconfigurationfile, clusters.conf

webserver –webserverlogsforthisinstanceandsymboliclinkstowebserverfilesintheinstallationdirectory

©CopyrightPivotalSoftwareInc,2013-2016 10 3.1.1

Page 11: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

SettingtheGreenplumCommandCenterEnvironmentToenablethe gpadmin usertoexecuteCommandCenterutilitiessuchas gpcmdr ,followthesestepstosetuptheGreenplumCommandCenterenvironment.

1. Addthe GPPERFMONHOME environmentvariabletoyourstartupshellprofile(suchas ~/.bashrc ).SetthevariabletotheGreenplumCommandCenterhomedirectory.

GPPERFMONHOME=/usr/local/greenplum-cc-websource$GPPERFMONHOME/gpcc_path.sh

Ensurethatthe $GPPERFMONHOME/gpcc_path.sh filehasentriesforthe greenplum_path.sh fileandthe MASTER_DATA_DIRECTORY environmentvariable.SeetheGreenplumDatabaseInstallationGuidefordetails.

2. Saveandsourcethe .bashrc file:

$source~/.bashrc

©CopyrightPivotalSoftwareInc,2013-2016 11 3.1.1

Page 12: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CreatingthegpperfmonDatabaseThistopicdescribeshowtocreatetheCommandCenter gpperfmon databaseandenablethedatacollectionagents.ThistaskmustbecompletedonetimefortheGreenplumDatabasesystem,beforeyoucreateaGreenplumCommandCenterinstance.

Whenthedatacollectionagentsareenabled,theirprocessesarestartedandstopped(using gpstart and gpstop )ontheGreenplumsegmenthostsalongwiththeGreenplumDatabaseserverprocesses.

Greenplumprovidesa gpperfmon_install utilitythatperformsthefollowingtasks:

CreatestheCommandCenterdatabase(gpperfmon).

CreatestheCommandCentersuperuserrole( gpmon ).

ConfiguresGreenplumDatabaseservertoacceptconnectionsfromthe gpmon role(editsthe pg_hba.conf and .pgpass files).

SetstheCommandCenterserverconfigurationparametersintheGreenplumDatabaseserver postgresql.conf files.

The gpperfmon_install utilityandtheagentsarepartoftheGreenplumDatabasesoftwaredistribution.ThetasksinthistopiccanbeperformedbeforeoraftertheCommandCentersoftwareisinstalled.

EnablingtheCollectionAgents1. LogintotheGreenplummasterhostasthe gpadmin user.

$su-gpadmin

2. SourcethepathfilefromtheGreenplumDatabaseinstallationdirectory:

#source/usr/local/greenplum-db/greenplum_path.sh

3. Runthe gpperfmon_install utilitywiththe --enable option.YoumustsupplytheconnectionportoftheGreenplumDatabasemasterserverprocess,andsetthepasswordforthe gpmon superuserthatwillbecreated.Forexample:

$gpperfmon_install--enable--passwordchangeme--port5432

Note:The gpperfmon_install utilitycreatesentriesforthe gpmon userinthe $MASTER_DATABASE/pg_hba.conf file.SeegpmonUserAuthenticationfornotesaboutrestrictingthegpmonuser’saccesstodatabases.Thepasswordyouspecifyissavedina .pgpass fileinthe gpadmin user’shomedirectory.SeeChangingthegpmonPasswordforstepstochangethe gpmon password.

4. Whentheutilitycompletes,restartGreenplumDatabaseserver.Thedatacollectionagentswillnotstartuntilthedatabaseisrestarted.

$gpstop-r

5. Usingthe ps command,verifythatthedatacollectionprocessisrunningontheGreenplummaster.Forexample:

$ps-ef|grepgpmmon

6. RunthefollowingcommandtoverifythatthedatacollectionprocessesarewritingtotheCommandCenterdatabase.Ifallofthesegmentdatacollectionagentsarerunning,youshouldseeonerowpersegmenthost.

$psqlgpperfmon-c'SELECT*FROMsystem_now;'

Thedatacollectionagentsarenowrunning,andyourGreenplumsystemnowhasagpperfmondatabaseinstalled.ThisisthedatabasewhereCommandCenterdataisstored.Youcanconnecttoitasfollows:

$psqlgpperfmon

©CopyrightPivotalSoftwareInc,2013-2016 12 3.1.1

Page 13: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ConfiguringaStandbyMasterHost(ifenabled)1. Copythe $MASTER_DATA_DIRECTORY/pg_hba.conf filefromyourprimarymasterhosttoyourstandbymasterhost.Thisensuresthattherequiredconnectionoptionsarealsosetonthestandbymaster.

2. Copyyour ~/.pgpass filefromyourprimarymasterhosttoyourstandbymasterhost.Thisfileusuallyresidesinthe gpadmin user’shomedirectory.Notethatthepermissionson .pgpass mustbesetto600(forexample: chmod 0600 ~/.pgpass ).

gpmonUserAuthenticationThe gperfmon_install utilityaddsthe gpmon usertothe pg_hba.conf authorizationconfigurationfileentriesallowinglocalconnectionstoanydatabaseintheGreenplumcluster.GreenplumCommandCenterrequiresthatthe gpmon userhaveaccessto gpperfmon andeverydatabasethatCommandCenterwillmonitor.Sincethe gpmon roleisaGreenplumDatabasesuperuser,youmaywishtorestricttherolefromaccessingotherdatabases.Editthe$MASTER_DATA_DIRECTORY/pg_hba.conf andedittheselines:

localgpperfmongpmonmd5hostallgpmon127.0.0.1/28md5

List gpperfmon andthedatabasesyouwanttomonitorwithCommandCenterinthesecondfield:

localgpperfmon,userdb1,userdb2gpmonmd5hostgpperfmon,userdb1,userdb2gpmon127.0.0.1/28md5

SeeChangingthegpmonPasswordforstepstochangethe gpmon user’spassword.

©CopyrightPivotalSoftwareInc,2013-2016 13 3.1.1

Page 14: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

UpgradingGreenplumCommandCenterThissectionprovidesstepsforupgradingPivotalGreenplumCommandCentertoanewversion.

UpgradingGreenplumCommandCenterrequiresinstallingthenewdistribution,andthenmigratingCommandCenterinstancesfromapreviousinstallation.

AnewGreenplumCommandCentersoftwarereleasemaybeinstalledinthesameparentdirectoryasthecurrentrelease,bydefault /usr/local .Theinstallerupdatesthesymboliclink greenplum-cc-web topointtothenewreleasedirectoryandleavestheoldreleasedirectoryinplace.Afterthesoftwareisinstalled,runthe gpcmdr--

migratecommandtorecreateyourCommandCenterinstances.

InstalltheNewSoftwareRelease1. Loginasthe gpadmin user.

2. Sourcethe greenplum_path.sh and gpcc_path.sh filesfromthecurrentrelease:

$source/usr/local/greenplum-db/greenplum_path.sh$source/usr/local/greenplum-cc-web/gpcc_path.sh

3. DownloadthelatestCommandCenterreleasefromPivotalNetwork .InstallerfilesareavailableforLinux64-bitplatforms,andhavenamesintheformat:

greenplum-cc-web-X.X.X-PLATFORM.zip

4. Unziptheinstallerfile.Forexample:

#unzipgreenplum-cc-web-X.X.X-PLATFORM.zip

5. Launchtheinstallerforthenewreleasewiththebashshell:

$/bin/bashgreenplum-cc-web-X.X.X-PLATFORM.bin

Note:Theinstallerrequireswritepermissionintheinstallationdirectory( /usr/local ,bydefault).Ifthe gpadmin userdoesnothavewritepermissionintheinstallationdirectory,runtheinstallationas root .Youwillneedtochangefileownershipandpermissionsafterthesoftwareisinstalled.

6. Readthroughthelicenseagreement.Whenyoureachthebottom,type yes toacceptthelicenseagreement.

7. Theinstallerpromptsyoutoprovideaninstallationpath.EnterafullpathorpressENTERtoacceptthedefault, /usr/local .Youmusthavewritepermissioninthedirectoryyouspecify.

8. Ifyourantheinstallationas root oranyuserotherthan gpadmin ,changetheownershipandpermissionsoftheinstallationdirectory:

#chown-Rgpadmin:gpadmin/usr/local/greenplum-cc-web-versionx.x#chmod-R755/usr/local/greenplum-cc-web-versionx.x

Changetothe gpadmin userbeforeyoucontinuetothenextstep:

#su-gpadmin

9. EnsurethatyouhaveacurrenthostfilelistingthenamesofalloftheotherhostsparticipatingintheGreenplumDatabasecluster,includingthestandbymasterhost.ThehostnamesmustberesolvableinDNS.

10. As gpadmin ,runthe gpccinstall utilitytoinstallthenewCommandCenterfilesonallhostslistedinthehostfile:

$gpccinstall-fhostfilename

where hostfilename isthenameofthehostfileyoucreated.

©CopyrightPivotalSoftwareInc,2013-2016 14 3.1.1

Page 15: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

MigrateCommandCenterInstancesAfterthenewCommandCentersoftwareisinstalled,migrateyourinstancesbyrunningthe gpcmdr--

migratecommand.

Tomigrateallinstancesfromapreviousinstallation,run gpcmdr--migrate

withnoarguments.Forexample:

$gpcmdr--migrate

Tomigrateasingleinstance,run gpcmdr--migrate<instance_name>

and,whenprompted,provideitsfullinstallationpath.Forexample:

$gpcmdr--migratemyinstance

Customchangestothe ssh-wrapper filearenothandledbyinstancemigration.SeeConfigurationFileReferenceforinformationaboutthe ssh-wrapperfile.Ifyouhavesetacustom ssh pathinthisfile,youmustcopyittothecurrentinstallation.

Forexample:

cp/usr/local/greenplum-cc-web-3.0.0/bin/ssh-wrapper/usr/local/greenplum-cc-web/bin

SeeCreatingGreenplumCommandCenterConsoleInstancesforinstructionstocreatenewinstanceswith gpcmdr--setup

.

©CopyrightPivotalSoftwareInc,2013-2016 15 3.1.1

Page 16: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

UninstallingGreenplumCommandCenterTouninstallGreenplumCommandCenter,youmuststopboththeCommandCenterConsoleanddisablethedatacollectionagents.Optionally,youmayalsoremoveanydataassociatedwithGreenplumCommandCenterbyremovingyourCommandCenterConsoleinstallationandtheCommandCenterdatabase.

1. StopCommandCenterConsoleifitiscurrentlyrunning.Forexample:

$gpcmdr--stop

2. RemovetheCommandCenterinstallationdirectoryfromallhosts.Forexample:

$rm-rf/usr/local/greenplum-cc-web-version

3. DisabletheDataCollectionAgents.

a. LogintothemasterhostastheGreenplumadministrativeuser( gpadmin ):

$su-gpadmin

b. Editthe $MASTER_DATA_DIRECTORY/postgresql.conf fileanddisablethedatacollectionagents:

gp_enable_gpperfmon=off

c. Removeorcommentoutthegpmonentriesin pg_hba.conf .Forexample:

#localgpperfmongpmonmd5#hostgpperfmongpmon0.0.0.0/0md5

d. DroptheCommandCentersuperuserrolefromthedatabase.Forexample:

$psqltemplate1-c'DROPROLEgpmon;'

e. RestarttheGreenplumDatabaseinstance:

$gpstop-r

f. CleanupanyuncommittedCommandCenterdataandlogfilesthatresideonthemasterfilesystem:

$rm-rf$MASTER_DATA_DIRECTORY/gpperfmon/data/*$rm-rf$MASTER_DATA_DIRECTORY/gpperfmon/logs/*

g. IfyoudonotwanttokeepyourhistoricalCommandCenterdata,dropthegpperfmondatabase:

$dropdbgpperfmon

©CopyrightPivotalSoftwareInc,2013-2016 16 3.1.1

Page 17: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

RunningGreenplumCommandCenter2.xinParallelWith3.xTousefeaturesofGPCC2.xnotavailablein3.x,youcanrunaGPCC2.xinstanceonaseparateportonthemasterhostandmanageitindependentlyfromGPCC3.x.

ContinueRunninganInstalledGPCC2.xVersionAfteryouinstallGPCC3.x:

1. Run gpcmdr--status toidentifyanavailableportthatisnotinusebyaGPCC3.xinstance.

2. Changethesymboliclinkinyourinstallationdirectorytothe2.xversion:

$ln-sfn/usr/local/greenplum-cc-web-2.x.x/usr/local/greenplum-cc-web

3. Edit $GPPERFMONHOME/instances/<instance_name>/conf/lighttpd.conf .Changethe server.port parametersoitdoesnotconflictwiththe3.xport.Forexample:

server.port=28090

Changethesevenoccurrencesof greenplum-cc-web totheabsolutepathofthe2.xinstallationdirectory.Forexample:

server.document-root="/usr/local/greenplum-cc-web/./instances/demo/web"

becomes

server.document-root="/usr/local/greenplum-cc-web-2.5.0/instances/demo/web"

4. StarttheGPCC2.xinstance:

$gpcmdr--start<instance_name>

5. Changethesymboliclinkinyourinstallationdirectorytopointtoyourcurrent3.xversion:

$ln-sfn/usr/local/greenplum-cc-web-3.0.0/usr/local/greenplum-cc-web

InstallGPCC2.xinAdditiontoGPCC3.xAfteryouinstallGPCC3.x:

1. Run gpcmdr--status toidentifyanavailableportnotinusebyaGPCC3.xinstance.

2. DownloadtheGPCC2.5.0installerfromPivotalNetwork .

3. Unzipandruntheinstaller:

$unzipgreenplum-cc-web-2.5.0-RHEL5-x86_64.zip$bashgreenplum-ccweb-2.5.0-RHEL5-x86_64.bin

Thiswillchangethesymlinkat /usr/local/greenplum-cc-web totheGPCC2.5.0installationdirectory.Note:Donotrun gpccinstall ,justthedownloadedinstallerbinary.

4. CreateaGPCC2.xinstance:

$gpcmdr--setup

SpecifyaportthatisnotusedbyanyexistingGPCC3.xinstances.

5. Edit $GPPERFMONHOME/instances/<instance_name>/conf/lighttpd.conf .

©CopyrightPivotalSoftwareInc,2013-2016 17 3.1.1

Page 18: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

Changethesevenreferencestothe greenplum-cc-web symboliclinktotheabsolutepathoftheGPCC2.xinstallationdirectory.Forexample:

server.document-root="/usr/local/greenplum-cc-web/./instances/demo/web"

becomes

server.document-root="/usr/local/greenplum-cc-web-2.5.0/instances/demo/web"

6. StarttheGPCC2.xinstance:

$gpcmdr--start<instance_name>

Attheprompt“Doyouwanttostartthebetaserver?”enter N .

7. ChangethesymboliclinkinyourinstallationdirectorytopointtoyourcurrentGPCC3.xversion:

$ln-sfn/usr/local/greenplum-cc-web-3.0.0/usr/local/greenplum-cc-web

ManagingConcurrentGPCC2.xand3.xVersionsThe gpcmdr utilitymanagestheinstancesfortheversionofGPCCinthecurrent gpcc_path.sh .Assumingyour.bashrcorothersourcefilecontainssource$GPPERFMONHOME/gpcc_path.sh ,toswitchbetweenversions,justmodifythesymboliclink greenplum-cc-web (inthe /usr/local directory,bydefault)topointtotheappropriateversion.

Tomanage2.xinstances:

$ln-sfn/usr/local/greenplum-cc-web-2.x.x/usr/local/greenplum-cc-web

Tomanage3.xinstances:

$ln-sfn/usr/local/greenplum-cc-web-3.x.x/usr/local/greenplum-cc-web

©CopyrightPivotalSoftwareInc,2013-2016 18 3.1.1

Page 19: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CreatingGreenplumCommandCenterConsoleInstancesACommandCenterConsoleinstanceisawebserverprovidinganHTML5graphicalconsoleapplicationtomonitorsystemmetricsandperformsomeadministrativetasksforasingleGreenplumDatabasecluster.

TheCommandCenterConsolerunsonthegpmonwswebserver.Thedefaultwebserverportis28080.Configurationfiles,logfiles,andruntimefilesforeachCommandCenterinstancearemanagedinasubdirectoryofthe $GPPERFMON/instances directory.

IfyouhavemultipleGreenplumDatabaseinstances,youcancreateseparateCommandCenterConsoleinstancesforeachofthem.Eachseparateconsoleinstanceoperatesonauniqueportandhasitsownuniqueconfigurationoptions.Amulti-clusterviewmaybeenabledtoallowyoutoviewstatusforallclusters.SeeEnablingMulti-ClusterSupportformoreinformation.

Formoreinformationaboutthewebserver,seeWebServerAdministration.

TheCommandCenterConsolesupportscurrentbrowserversionsofChrome,Safari,Firefox,andInternetExplorer.

BeforeYouBeginEnsurethatthefollowingprerequisitesaresatisfied:

GreenplumCommandCentersoftwareisinstalled.SeeInstalltheGreenplumCommandCenterSoftware.

Thegpperfmondatabaseiscreatedandthedatacollectionagentsarerunning.SeeCreatingthegpperfmonDatabase.

AnycertificatesorKerberoskeytabfilesneededforencryptionanduserauthenticationareinstalled.SeeSecuringaGreenplumCommandCenterConsoleInstance.

Ifthe gpmon useristobeauthenticatedwithKerberos,installthekeytabfileforthe gpmon KerberosprincipalontheGreenplummasterandstandbyhostsandrun kinit gpmon beforeyoubegintocreatetheCommandCenterConsoleinstance.SeeSecuringthegpmonDatabaseUserformoreinformation.

The gpcmdr--setup

command-lineutilitysetsuptheCommandCenterinstance.Thecommandcanberuninteractively,oryoucancreateaconfiguration

fileandrunthecommandnon-interactively.Ifyouuseaconfigurationfile,youcancreatemultipleCommandCenterinstancesatonce.

Creatinganinstanceinteractively

Creatinganinstancewithaconfigurationfile

CreatingtheGreenplumCommandCenterInstance(Interactive)FollowthestepsbelowtocreateanewCommandCenterConsoleinstance.Toacceptthedisplayeddefaultvaluesforanyparametersatconfigurationtime,presstheENTERkey.TomonitormultipleGreenplumDatabaseclusters,runthesetuputilityseparatelytocreateaninstanceforeachcluster.

1. LoginastheGreenplumadministrator( gpadmin )andsourcethe $GPPERFMON/gpcc_path.sh file.

2. WiththeGreenplumDatabaseinstancerunning,launchthesetuputility.Forexample:

$gpcmdr--setup

3. ProvideaninstancenamefortheGreenplumDatabaseinstancemonitoredbythisConsole.

4. Provideadisplaynamefortheinstance.ThisnameisshownintheConsoleuserinterface.Thispromptdoesnotappearifthemasterhostisremote.

5. Select y or n tospecifyiftheGreenplumDatabasemasterforthisinstanceisonaremotehost.NotethatConsoleperformanceisbetterwhentheConsoleandGreenplumDatabasemasterareonthesamehost.Ifthemasterhostisremote,enter y andenterthehostnameorIPaddressofthemasterattheprompt.

6. ProvidetheportnumberfortheGreenplumDatabasemasterinstance.

7. ProvideaportnumberfortheCommandCenterConsolewebserver.Thedefaultis28080.

8. Enter y totheprompt Enablekerberosloginforthisinstance? touseKerberosauthentication.Tousethisfeature,KerberosauthenticationmustbeenabledforGreenplumDatabaseandtheKerberosadministratormusthavecreatedakeytabfileforCommandCenter.SeeEnablingKerberosAuthenticationwithGreenplumCommandCenterfordetails.Ifyouenter n youcanenableKerberosauthenticationlaterusingthe gpcmdr--

©CopyrightPivotalSoftwareInc,2013-2016 19 3.1.1

Page 20: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

krbenable command.IfyouchoosetoenableKerberosauthentication:

a. Attheprompt Enter web server name for this instance: enterthenameofthehostfromtheKerberosprincipal.Theprincipalnameisintheformat HTTP/<host>@<realm> .ThehostmustbeenteredinthesameformatastheKerberosprincipalandshouldexcludetheportnumber.

b. Attheprompt Enter the GPDB Kerberos service name: enterthenameoftheKerberosserviceprincipalforGreenplumDatabase.c. Attheprompt Choose Kerberos mode: enterthenumberoftheKerberosmodeyouwanttouse.SeeEnablingAuthenticationWithKerberosforadescriptionoftheseoptions.

d. Attheprompt Enter the path to the keytab file: enterthefullpathtothekeytabcontainingthewebserverprincipal.IfyouaresettingupthisinstanceontheGreenplummaster,thekeytabfilemaybethesameoneusedforGreenplumDatabase.

9. Enter y toenableSSLconnectionsfortheCommandCenterConsole,or n ifyoudonotwantSSL.Note:Becausedatabaselogininformationissentoverthenetwork,itisstronglyrecommendedtouseSSLtoencryptthesecommunications.YouareaskedtospecifythelocationofyourX509certificatefile.Enterthefullpathtothecertificatefile.Thepathyouenterisaddedtothe app.conf

file.n

10. Enter y or n tospecifywhetheryouwantthisinstallationcopiedtoastandbymaster.Ifyouenter y ,youarepromptedforthestandbymasterhostname.

11. StarttheConsoleandlogin.SeeConnectingtotheGreenplumCommandCenterConsole.

12. YoucanalsoconfigureauthenticationsothatotherGreenplumuserscanlogintotheConsole,seeConfiguringAuthenticationfortheCommandCenterConsolefordetails.

CreatingtheCommandCenterConsoleInstance(Non-interactive)Itcanbeusefultorun gpcmdr--

setupnon-interactively,takinginputfromafile.Forexample,youcouldinstallGPCCandcreateCommandCenterinstances

aspartofaGreenplumclusterinstallationscript.Toaccomplishthis,createaconfigurationfileandsupplyittothe gpcmdr utilityusingthe --config_fileoption:

gpcmdr--setup--config_filefile

TheconfigurationfileissimilartoaWindowsINIfile,containingoneormoresectionsbeginningwithasectionheaderinsquarebraces.Parametersintheoptional [DEFAULT] sectionapplytoallsubsequentsectionsandmaybeoverridden.Eachsectionotherthan [DEFAULT] definesaCommandCenterConsoleinstancetocreate.

Parametersarespecifiedone-per-lineasname-valuepairsseparatedwithequalssigns( = )orcolons( : ).Commentsbeginwithanumbersign( # )orsemicolon( ; )andcontinuetotheendoftheline.

Hereisanexampleconfigurationfile:

[DEFAULT]#defaultsapplytoallinstancesremote_db:falseenable_copy_standby:truestandby_master_host:smdwenable_kerberos:falseenable_ssl:trueenable_user_import_cert:truessl_cert_file:/etc/ssl/certs/cert.pemenable_user_import_dhe:falseenable_reuse_dhe:true

[production]master_hostname:mdwinstance_name:proddisplay_name:Productionmaster_port:5432web_port:28080

[development]master_hostname:mdwinstance_name:devenable_copy_standby:false;overridedisplay_name:Developmentmaster_port:5532web_port:28090

©CopyrightPivotalSoftwareInc,2013-2016 20 3.1.1

Page 21: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

SeeSetupConfigurationFileforadetaileddescriptionofthesetupconfigurationfilesyntaxandparameters.

StarttheCommandCenterConsoleInstanceStarttheGreenplumCommandCenterConsoleinstancebyentering:

gpcmdr--start

Ifyoudonotspecifyaninstancename,allCommandCenterConsoleinstancesarestarted.Tostartaparticularinstance,youcanspecifythenameoftheinstance.Forexample:

gpcmdr--startinstance_name

SeeAdministeringGreenplumCommandCenterforacompletelistofadministrativecommands.

©CopyrightPivotalSoftwareInc,2013-2016 21 3.1.1

Page 22: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ConnectingtotheGreenplumCommandCenterConsoleOpentheCommandCenterConsoleinasupportedbrowserusingthecorrecthostnameandport.Forexample,toopenaCommandCenterinstancerunningonport28080onthelocalhostwithSSL,enterthefollowingURLinthebrowser:

https://<master_host_name>:28080/

Attheloginprompt,entertheusernameandpasswordofaGreenplumrolethathasbeenproperlyconfiguredtoallowauthenticationtoGreenplumCommandCenter,thenclickLogin.ThisopenstheDashboardpageoftheCommandCenterConsole,whichprovidesagraphicalsystemsnapshotandasummaryviewofactivequeries.SeetheDashboardforinformationabouttheDashboardview.

©CopyrightPivotalSoftwareInc,2013-2016 22 3.1.1

Page 23: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

GreenplumCommandCenterUserGuideTheGreenplumCommandCenterwebinterfaceisamanagementtoolthatprovidessystemstatusandquerymonitoringfacilitiesforGreenplumDatabaseadministratorsandusers.

CommandCenterviewsallowyoutoinstantlyviewtheoverallstatusoftheGreenplumDatabasesystem.Youcandrilldowntoseedetailsabouthosts,databasesegments,queries,andCPU,memory,anddiskresourceutilization.

ThefollowingtopicsdescribetheinformationdisplayedoneachCommandCenterview.

DashboardTheDashboarddisplayswhenyoufirstlogintotheCommandCenter.ItshowsanoverviewofthestatusoftheGreenplumDatabaseclustertheCommandCentermanagesandprovideseasyaccesstodetailedinformationaboutanyaspectofsystemstatus.

QueryMonitorViewcurrentrunningandqueuedqueries.Selectaquerytoviewitsquerytextandexecutionplan.Withproperpermissions,choosequeriesandcancelthem.

HostMetricsViewreal-timestatisticsbyserverinatableformat.

ClusterMetricsViewchartsofcurrentandrecentstatisticsforallhosts(excludingmasterandstandby).

HistoryViewqueriesandhistoricalchartsofstatisticsforaselectedtimeperiod,optionallyfilteredbydatabaseanduser.

System>SegmentStatusViewastatussummaryforallprimaryandmirrorsegmentsanddetailsforeachsegment.

System>StorageStatusViewthecurrentpercentagediskspaceinuseformasterandsegmenthosts,ahistoricalchartofsegmenthostdiskusage,andcurrentdiskusagebyhost.

Admin>PermissionsViewpermissionslevelsforCommandCenterusers.UserswithAdminpermissioncanchangepermissionlevels.

Admin>AuthenticationViewtheGreenplumDatabase pg_hba.conf host-basedauthenticationfile.UserswithAdminpermissioncaneditthefile.

©CopyrightPivotalSoftwareInc,2013-2016 23 3.1.1

Page 24: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

DashboardTheDashboarddisplayswhenyoufirstsignintoPivotalGreenplumCommandCenter.TheDashboardprovidesaquickviewofthecurrentsystemstatus,SegmentHealth,Queries,CPU,Memory,andDiskusage.Clickingonapanelprovidesmoredetailedinformationaboutthemetric.

SystemInformationThefollowingsysteminformationisdisplayedatthetopofthepage.

UptimeTheelapsedtimesincetheGreenplumDatabasesystemwaslaststarted.

GPDBVersionTheversionoftheGreenplumDatabasesoftwarethemonitoredclusterisrunning.

ConnectionsThenumberofactiveGreenplumDatabasesessions(clientconnections).

LastSyncDateandtimethedatawaslastsynchronized.TheCommandCenteruserinterfaceupdatesviewswithlivedataevery15seconds.

SystemSummaryTheSegmentHealthsectionoftheDashboardprovidesaquickoverviewofthestatusoftheGreenplumDatabasemanagedbythisinstanceoftheCommandCenter.

ClickingtheSegmentHealthpaneldisplaystheSegmentStatusCommandCenterpage.

DatabaseStateisthecurrentstateoftheGreenplumDatabasesystem.Thestatecanbeoneofthefollowing:

Normal:Thedatabaseisfunctioningwithnomajorerrorsorperformanceissues.

Segment(s)Down:Thedatabaseisinchange-trackingmodeorresyncmode.Overallperformanceandsystemreliabilityisgreatlyreduced.SeethePivotalGreenplumDatabaseSystemAdministratorGuideforinformationaboutresolvingthiscondition.

DatabaseUnreachable:TheGreenplumPerformanceMonitoragentcannotconnecttothedatabase.Thedatabaseislikelydown.SeethePivotalGreenplumDatabaseSystemAdministratorGuidefortroubleshootinginformation.

Unbalanced:Somesegmentsarenotrunningintheirpreferredroles.Thatis,primariesarerunningasmirrorsandmirrorsarerunningasprimaries,resultinginunbalancedprocessing.

Resyncing:Thedatabaseisperformingarecoveryorrebalanceoperation.

ThebargraphintheSegmentHealthsectionshowstheupordownstatusofalldatabasesegmentsinyourPivotalGreenplumDatabasesystem.Acolorindicatorandassociatednumberindicatethenumberofdatabasesegmentsthatarecurrentlyinthatparticularstate.Segmentscanhavethefollowingstates:

Up(Green)

Down(Red)

DiskUsageSummaryThischartdisplaystotaldiskusageanddiskavailablefortheGreenplummasterhostandsegmenthostsatthelastsynchronization.Hoveroverthecharttoseetheamountofdiskused,free,andtotal.

QueriesThisgraphdisplaysasummaryviewofactiveandqueuedqueriesforthelast60minutes.ClickonthecoloreddotnexttotheRunningorQueuedlabeltotogglethelineonoroff.Atleastonelinemustbevisibleatalltimes.Hoveroverthegraphtodisplaythenumberofqueriesforeachvisiblelineatthatpointintime.

©CopyrightPivotalSoftwareInc,2013-2016 24 3.1.1

Page 25: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CPUThisgraphdisplaysaverageCPUusageacrosstheentirecluster,forthelast60minutes.Thegraphdisplaysseparatelinesforsystemprocessesanduserprocesses.TheuserCPUusageincludestheGreenplumdatabasemaster,standby,andsegmentprocesses.ClickonthecoloreddotnexttotheSystemorUserlabeltotogglethatlineonoroff.Atleastonelinemustbevisibleatalltimes.

HoveringthecursoroveralineinthegraphdisplaysasmallwindowwiththepercentageofCPUusedatthatpointintimeforthevisiblelinesandthetotalifboththesystemanduserlinesarevisible.

MemoryThisgraphdisplaystheaveragepercentofmemoryusedacrosstheentireclusteroverthelast60minutes.Hoveroverthelinetodisplaythepercentofmemoryusedatthatpointintime.

AlertsAdminandOperatorpermissionlevelsonly

TheAlertspaneldisplaysrecentmessagesfromtheGreenplumDatabase pg_log logfile.Thepanelisupdatedateachsynchronization.Filterthemessagesbyseveritylevelusingthecontrolsatthetoprightofthepanel.

©CopyrightPivotalSoftwareInc,2013-2016 25 3.1.1

Page 26: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

QueryMonitorTheQueryMonitorviewallowsyoutoviewdetailedinformationforactivequeriesrunningontheGreenplumDatabasesystem.UserswithAdminorOperatorpermissioncanseeandcancelallusers’queries.

Dataiscollectedoncurrentlyrunningqueriesandthequerymonitormetricsareupdatedevery15seconds.Thetimeofthelastupdateandagraphicaltimershowingthetimeremainingbeforethenextupdatearedisplayedatthetopofthepage.

Withtheinformationavailableinthisview,GreenplumDatabaseadministratorscaneasily:

Understandhowthesystemisbeingused—bothinreal-timeandtrendingovertime.

Identifyanddiagnoseproblemquerieswhiletheyarerunning,detectskew,findrunawayqueries,andsoon.

Reviewandbalancethequeryloadonthesystembybetteroptimizingandschedulingthequeryload.

Cancelqueriesthatdisruptsystemperformance.

QueryMetricsTheQueryMonitortabledisplaysthefollowingcolumnsforqueries.

QueryIDAnidentificationstringforthequery.IntheConsole,thislookslike“1295397846-56415-2”.CommandCentergeneratesthisIDbycombiningthequeryrecord’s tmid , ssid ,and ccnt fields.(Seequeries_*intheCommandCenterDatabaseReference.)

StatusThestatusofthequery.Thiscanbeoneofthefollowing:

Queued:thequeryhasnotyetstartedtoexecute

Running:executionhasstarted,isnotyetcomplete

Done:completedsuccessfully

Cancelling:cancelrequestsent,cancelpending

Cancelled:terminated,nolongerrunning

UserTheGreenplumDatabaseuserwhosubmittedthequery.

DatabaseThenameofthedatabasethatwasqueried.

SubmitTimeThetimethequerywassubmittedtothequeryplanner.

QueueTimeTheamountoftimethequeryhasbeen(orwas)inqueueawaitingexecution.

RunTimeTheamountoftimesinceexecutionbegan.

CPU%(Activequeriesonly.)CurrentCPUpercentaverageforallprocessesexecutingthisquery.Thepercentagesforallprocessesrunningoneachsegmentareaveraged,andthentheaverageofallthosevaluesiscalculatedtorenderthismetric.CurrentCPUpercentaverageisalwayszeroinhistoricalandtaildata.

CPUSkewTheamountofCPUskew.CPUskewoccurswhenqueryexecutorprocessesforonesegmentuseadisproportionateamountofCPUcomparedtoprocessesforothersegmentsexecutingthequery.ThisvalueisthecoefficientofvariationfortheCPUusedbyprocessesrunningthisqueryoneachsegment,multipliedby100.Forexample,avalueof.95isshownas95.

RowSkewAmeasureofrowskewinthesystem.Rowskewoccurswhenonesegmentproducesadisproportionatenumberofrowsforaquery.ThisvalueisthecoefficientofvariationfortheRowsOutmetricofalliteratorsacrossallsegmentsforthisquery,multipliedby100.Forexample,avalueof.95isshownas95.

©CopyrightPivotalSoftwareInc,2013-2016 26 3.1.1

Page 27: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

QueueThenameoftheresourcequeueforthequery.

PriorityEachqueryinheritsthepriorityassignedtoitsresourcequeue.FormoreinformationaboutResourceQueuesandQueryPlans,refertotheGreenplumDatabaseAdministratorGuide.

UsingtheQueryMonitorControlsClickacolumnheadingtosorttherowsonthatcolumninascendingordescendingorder.

Clickthecheckboxattheleftofarowtochooseaquerytocancelorexport.Clickthecheckboxintheheadingrowtochooseallqueries.

ClickCancelQuerytocancelselectedqueries.

ClickExporttodownloadacomma-separatedvalues(CSV)textfilecontainingrowsfortheselectedqueries.Whennoqueriesareselected,allrowsareexported.Thedefaultfilenameis spreadsheet.csv .

ClickanyqueryIDtoseetheQueryDetails ,includingmetrics,thetextofthequery,andthequeryplan.

©CopyrightPivotalSoftwareInc,2013-2016 27 3.1.1

Page 28: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

HostMetricsTheHostMetricspagedisplaysatableofthehostsintheclusterwithstatisticscollectedatthemostrecentquantuminterval.Atthetop,LastSyncdisplaysthetimethestatisticswerelastupdated.

Clickacolumnheadertosortthetablebythatcolumn.Clickagaintotogglebetweenascendinganddescendingsort.Masterandstandbyhostsarenotincludedinthesortandarealwaysdisplayedfollowingthesortedlistofsegmenthosts.

Foreachserver,thefollowingcolumnsaredisplayed:

HostnameThehostnamenameoftheserver.

CPUTotal/Sys/User(%)ThetotalpercentageofCPUinuseisdisplayednexttoagraphillustratingtheCPUusedforsystemanduserprocesses.HoveroverthetablecelltoshowthepercentagesusedforsystemanduserprocessesandthepercentageCPUidle.

MemoryInUse(%)Thepercentageofhostmemoryinuseisdisplayednexttoagraphillustratingthememoryinuseandavailable.Hoveroverthetablecelltoseememoryusedandavailableingigabytes.

Memoryiscalculatedasfollows:

Total=MemTotalFree=MemFree+Buffers+CachedUsed=Total-Free

DiskR(MB/s)|SkewDiskreadrateinmegabytespersecondisdisplayednexttoagraphofcalculateddiskreadskew.HoveroverthetablecelltoseeaLow/Medium/Highratingfordiskskew.

DiskW(MB/s)|SkewDiskwriterateinmegabytespersecondisdisplayednexttoagraphofcalculateddiskwriteskew.HoveroverthetablecelltoseeaLow/Medium/Highratingfordiskwriteskew.

NetR(MB/s)|SkewNetworkreadrateinmegabytespersecondisdisplayednexttoagraphofcalculatednetworkreadskew.HoveroverthetablecelltoseeaLow/Medium/Highratingfornetworkreadskew.

NetW(MB/s)|SkewNetworkwriterateinmegabytespersecondisdisplayednexttoagraphofcalculatednetworkwriteskew.HoveroverthetablecelltoseeaLow/Medium/Highratingfornetworkwriteskew.

AboutSkewCalculationsDiskandNetworkskewratingsarecalculatedaseachserver’sstandarddeviationfromthemeancalculatedfromallsegmenthosts.

LowValueiswithin1standarddeviationfromthemean.(Note:ifthevarianceofthesetislessthan3,skewisconsideredlowregardlessofdeviationfrommean.)

ModerateValueisbetween1and2standarddeviationsfromthemean.

VeryHighValueisgreaterthan3standarddeviationsfromthemean.

©CopyrightPivotalSoftwareInc,2013-2016 28 3.1.1

Page 29: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ClusterMetricsTheClusterMetricspageshowsconsolidatedstatisticsforallsegmenthostsintheGreenplumcluster.Masterandstandbymasterhostsareexcludedfromthemetrics.

Thechartsdisplaymetricsforthelasttimeperiodsetbythecontrolinthetoprightcornerofthescreen.

UsetheShow/hideChartscontroltochoosewhichmetricstodisplay.

Hoveroveranyofthechartstoseevaluesforthemetricsatapointintimeinpop-upboxes.Thechartsaresynchronizedsothathoveringoveranychartshowsthesamepointintimeinallcharts.

Thecurrentvalueofametricisshownintheupperrightcornerofitschart.

Onchartswithmultiplemetrics,togglethedisplayforalineonoroffbyclickingtheline’slabelinthelegendatthetoprightofthechart.Atleastonelinemustbedisplayed.Alllinesareredisplayedatthenextquantuminterval.

Thepagehaschartsforthefollowingmetrics:

QueriesThenumberofqueriesrunningandthenumberofqueriesqueuedtorun.

CPUThepercentageCPUusedbysystemprocessesandthepercentageCPUusedbyuserprocesses.

MemoryPercentageofmemoryinuse.

Memoryiscalculatedasfollows:

Total=MemTotalFree=MemFree+Buffers+CachedUsed=MemTotal-Free

DiskI/ODiskreadandwriteratesinmegabytespersecond.

NetworkNetworkI/Oreadandwriteratesinmegabytespersecond.NetworkmetricsincludetrafficoverallNICs(networkinterfacecards),includinginternalinterconnectandadministrativetraffic.

LoadSystemloadaveragefor1-minute,5-minute,and15-minuteperiods.

SwapPercentageofswapspaceused.

©CopyrightPivotalSoftwareInc,2013-2016 29 3.1.1

Page 30: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

MonitoringMultipleGreenplumDatabaseClustersTheGreenplumCommandCenterMulti-clusterviewdisplayshealthstatusformultipleGreenplumDatabaseclusters.Thechartscanbedividedintocategories.

EachGreenplumDatabaseclusterthatappearsintheMulti-clusterviewmusthaveitsownCommandCenterinstance.TheMulti-clusterviewishostedonasingle,designatedmasterCommandCenterinstance.Themasterinstanceretrievesthehealthstatusdatafromeachoftheclusters’CommandCenterinstances.

Clickingthestatuspanelforaclusterloadsthatcluster’sCommandCenterintoanewbrowserwindow.Ifauto-loginisenabledinthemulti-clusterconfigurationfile,theloginscreenisbypassedandtheDashboardisdisplayed.

Multi-clustersupportisenabledbydeployingaconfigurationfiletotheCommandCenterinstancedirectories.SeeEnablingMulti-ClusterSupportforinstructionstosetuptheMulti-clusterpage.

Bydefault,anyCommandCenterusermayviewmulti-clusterstatus.Accesstoclusterscanberestrictedinthemulti-clusterconfigurationfile.

TheMulti-clusterviewdisplaysthefollowinginformationforeachcluster.

ClusterNameThenameforthecluster,asspecifiedinthemulti-clusterconfigurationfile.

DatabaseStateThecurrentstateoftheGreenplumDatabasecluster.Thestatecanbeoneofthefollowing:

Normal:Thedatabaseisfunctioningwithnomajorerrorsorperformanceissues.

Segment(s)Down:Thedatabaseisinchange-trackingmodeorresyncmode.Overallperformanceandsystemreliabilityisgreatlyreduced.SeethePivotalGreenplumDatabaseSystemAdministratorGuideforinformationaboutresolvingthiscondition.

DatabaseUnreachable:TheGreenplumPerformanceMonitoragentcannotconnecttothedatabase.Thedatabaseislikelydown.SeethePivotalGreenplumDatabaseSystemAdministratorGuidefortroubleshootinginformation.

Unbalanced:Somesegmentsarenotrunningintheirpreferredroles.Thatis,primariesarerunningasmirrorsandmirrorsarerunningasprimaries,resultinginunbalancedprocessing.

Resyncing:Thedatabaseisperformingarecovertyorrebalanceoperation.

UptimeTheelapsedtimesincetheGreenplumDatabasesystemwaslaststarted.

GPDBVersionTheversionoftheGreenplumDatabasesoftwareeachmonitoredclusterisrunning.

ConnectionsThenumberofactiveGreenplumDatabasesessions(clientconnections).

ActiveQueriesThenumberqueriesqueuedorcurrentlyexecutinginthedatabase.

©CopyrightPivotalSoftwareInc,2013-2016 30 3.1.1

Page 31: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

HistoryTheHistorypageallowsyoutodisplaysystemmetricsandqueriesexecutedduringaspecifiedtimeperiod.Queriesmayalsobefilteredbydatabaseand/oruser.

SetthetimeperiodtodisplaybyenteringdatesandtimesintheFromandTodateandtimefields.Youcanenterdatesbytypingthemintothedatefieldorbychoosingfromthepop-upcalendar.Enter24-hourtimesinHH:MMformat.

Torestrictqueriesthatdisplayinthequerytableatthebottomofthepage,enteraGreenplumdatabasenameintheDatabasefield,ausernameintheUserfield,orboth.Filteringbydatabaseanduseronlyaffectsthequeriesdisplayedinthetable.Themetricsdisplayedinchartsincludeallactivityduringtheselectedtimeperiod.

ClickSearchtodisplayresultsthatmatchyourcriteria.

Youcanclickanddragonacharttozoominonatimerange.ClickSearchtoupdatethequerylistandchartstotheselectedrange.

Scrollchartsleftorrightbyhoveringovertheedgeofthechartandclickinganarrow.Click‹or›tomoveinhalfsteps.Click«or»tomoveinfullsteps.

Inthequerylist,selectorhoveroveraquerytohighlightitsqueuedandruntimeinthecharts.

Chartsofthefollowingmetricsareavailable.Showorhidethematanytimewiththechecklistattheupperrightoftheview.

QueriesThenumberofqueriesrunningandthenumberofqueriesqueuedtorun.

CPUThepercentageCPUusedbysystemprocessesandthepercentageCPUusedbyuserprocesses.

MemoryPercentageofmemoryinuse.

DiskI/ODiskreadandwriteratesinmegabytespersecond.

NetworkNetworkI/Oreadandwriteratesinmegabytespersecond.NetworkmetricsincludetrafficoverallNICs(networkinterfacecards),includinginternalinterconnectandadministrativetraffic.

LoadSystemloadaveragefor1-minute,5-minute,and15-minuteperiods.

SwapPercentageofswapspaceused.

QueryMetricsTheQuerytabledisplaysqueriesthatwereactiveduringthespecifiedtimeperiod,includingqueriesthatstartedbeforeorfinishedafterthespecifiedtime.However,queriesthatarestillactivearenotincludedinthetable;thesequeriescanbeviewedontheQueryMonitorpage.

Thequerytablehasthefollowingcolumns:

QueryIDAnidentificationstringforthequery.IntheConsole,thislookslike“1295397846-56415-2”.

StatusThefinalstatusofthequery.Thiscanbeoneofthefollowing:

Done

Cancelled

UserTheGreenplumDatabaseuserwhosubmittedthequery.

DatabaseThenameofthedatabasethatwasqueried.

SubmitTimeThetimethequerywassubmittedtothequeryplanner.

©CopyrightPivotalSoftwareInc,2013-2016 31 3.1.1

Page 32: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

QueuedTimeTheamountoftimeaqueryspentinthequeuebeforeitwasexecuted.

RunTimeTheamountoftimethequeryrequiredtoproducearesult.

EndTimeThetimethequerycompletedorwascancelled.

CPUSkewTheamountofCPUskew.CPUskewoccurswhenqueryexecutorprocessesforonesegmentuseadisproportionateamountofCPUcomparedtoprocessesforothersegmentsexecutingthequery.ThisvalueisthecoefficientofvariationfortheCPUusedbyprocessesrunningthisqueryoneachsegment,multipliedby100.Forexample,avalueof.95isshownas95.

RowSkewAmeasureofrowskewinthesystem.Rowskewoccurswhenonesegmentproducesadisproportionatenumberofrowsforaquery.ThisvalueisthecoefficientofvariationfortheRowsOutmetricofalliteratorsacrossallsegmentsforthisquery,multipliedby100.Forexample,avalueof.95isshownas95.

QueueThenameoftheresourcequeueforthequery.

PriorityEachqueryinheritsthepriorityassignedtoitsresourcequeue.

FormoreinformationaboutResourceQueuesandQueryPlans,refertotheGreenplumDatabaseAdministratorGuide.

©CopyrightPivotalSoftwareInc,2013-2016 32 3.1.1

Page 33: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

SystemTheSystemviewprovidessystemmetricsforindividualhostsintheGreenplumclusterandfortheentirecluster.ClickHostMetricstodisplaymetricsforeachhost.ClickClusterMetricstodisplayconsolidatedmetricsfortheentirecluster.

SegmentStatus

StorageStatus

©CopyrightPivotalSoftwareInc,2013-2016 33 3.1.1

Page 34: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

SegmentStatusTheSegmentStatuspageprovidesahealthoverviewfortheGreenplumDatabasesegmentsanddetailsforeachprimaryandmirrorsegment.

SegmentSummaryGreenplumDatabaseismostefficientwhenallsegmentsareoperatingintheirpreferredroles.TheSegmentSummarypaneltellsyoutheoverallsegmentstatusandifanymirrorsareactingasprimaries.

TheSegmentSummarypanelprovidesthefollowinginformation:

DatabaseStateThedatabasestatecanbeoneofthefollowing:

Normal:Thedatabaseisfunctioningwithnomajorerrorsorperformanceissues.

Segment(s)Down:Thedatabaseisinchange-trackingmodeorresyncmode.Overallperformanceandsystemreliabilityisgreatlyreduced.SeethePivotalGreenplumDatabaseSystemAdministratorGuideforinformationaboutresolvingthiscondition.

DatabaseUnreachable:TheGreenplumPerformanceMonitoragentcannotconnecttothedatabase.Thedatabaseislikelydown.SeethePivotalGreenplumDatabaseSystemAdministratorGuidefortroubleshootinginformation.

Unbalanced:Somesegmentsarenotrunningintheirpreferredroles.Thatis,primariesarerunningasmirrorsandmirrorsarerunningasprimaries,resultinginunbalancedprocessing.

Resyncing:Thedatabaseisperformingarecovertyorrebalanceoperation.

MirrorsActingasPrimaryThenumberofmirrorsegmentsactingasprimarysegments.

RecommendedActionsSuggestsactionstoperformtorestoretheclustertobalance.Theseinclude:

RecoverandRebalance

Rebalance

Theseactionsareexecutedfromthecommandlineusingthe gprecoverseg Greenplummanagementutility.See gprecoverseg inthePivotalGreenplumDatabaseUtilityReferenceformoreinformation.

TotalSegmentsThetotalnumberofprimaryandmirrorsegmentsintheGreenplumcluster.

SegmentHostsThetotalnumberofsegmenthostsintheGreenplumcluster.

SegmentHealthTheSegmentHealthpanelcontainschartsforGreenplumDatabasesegments’status,replicationmode,andpreferredroles.

StatusNumbersofsegmentsthataredownandup.

ReplicationModeAchartthatshowsthenumberofsegmentsineachofthepossiblereplicationmodes.

NotSyncing:Theprimarysegmentandmirrorsegmentareactiveandallchangestotheprimarysegmenthavebeencopiedtothemirrorusingafileblockreplicationprocess.

ChangeTracking:Ifaprimarysegmentisunabletocopychangestoitsmirrorsegmentusingthefilereplicationprocess,itlogstheunsentchangeslocallysotheycanbereplicatedwhenthemirroragainbecomesavailable.Thiscanhappenifamirrorsegmentgoesdownorifaprimarysegmentgoesdownanditsmirrorsegmentautomaticallyassumestheprimaryrole.

Resyncing:Whenadownsegmentisbroughtbackup,administratorsinitiatearecoveryprocesstoreturnittooperation.Therecoveryprocesssynchronizesthesegmentwiththeactiveprimaryandcopiesthechangesmissedwhilethesegmentwasdown.

Synced:Onceallmirrorsandtheirprimariesaresynchronized,thesystemstatebecomessynchronized.

©CopyrightPivotalSoftwareInc,2013-2016 34 3.1.1

Page 35: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

PreferredRolesTheredportionofthePreferredRolechartshowsthenumbersofsegmentsthatnotoperatingintheirpreferredprimaryormirrorroles.Ifthechartisnotsolidgreen,theperformanceoftheGreenplumclusterisnotoptimal.

Primaryandmirrorsegmentsaredistributedevenlyamongthesegmenthoststoensurethateachhostperformsanequivalentshareoftheworkandprimarysegmentsandtheirmirrorsegmentsresideondifferentsegmenthosts.Whenaprimarysegmentgoesdown,itsmirroronanotherhostintheclusterautomaticallyassumestheprimaryrole,increasingthenumberofprimarysegmentsrunningonthathost.Thisunevendistributionoftheworkloadwillaffectqueryperformanceuntilthedownsegmentisrestoredandthesegmentsarereturnedtotheiroriginal,preferred,roles.

SegmentTableThetableatthebottomoftheSegmentStatuspagecontainsadetailedrowforeveryprimaryandmirrorsegmentintheGreenplumCluster.Thetablehasthefollowingcolumnsforeachsegment:

HostnameThenameofthesegmenthostwherethesegmentisrunning.

AddressThenetworkinterfaceonthesegmenthostforthesegment.

PortTheportnumberassignedtothesegment.

DBIDTheuniqueidentifierforthesegmentinstance.

ContentIDThecontentidentifierforthesegment,from0tothenumberofsegmentsminus1.AprimarysegmentanditsmirrorhavethesameContentID.Themasterandstandbymaster,whichhaveContentID−1,areexcludedfromthetable.

Status“UP”ifthesegmentisrunning,“DOWN”ifthesegmenthasfailedorisunreachable.

RoleThesegment’scurrentrole,either“primary”or“mirror”.

PreferredRoleThesegment’sintendedrole,either“primary”or“mirror”.

ReplicationModeThereplicationstatusforthesegment.SeeSegmentHealthforpossiblevalues.

LastEvent|[Total]Thedateandtimeoflastsegmenthealth-relatedactivity.Clicktodisplayalistofrecentevents.

©CopyrightPivotalSoftwareInc,2013-2016 35 3.1.1

Page 36: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

StorageStatusTheStorageStatuspageshowscurrenthistoricaldiskusageforGreenplummasterandsegmenthosts.

DiskUsageSummaryYoucanseecurrentdiskspaceinuse,spacefree,andtotalspaceintheDiskUsageSummarypanel.Diskspacemetricsforthesegmenthosts(GPSegments)andthemaster(GPMaster)areshowninseparatebarcharts.

TheGPSegmentsbarchartshowscombineddiskspaceforallsegments.

TheGPMastersbarchartshowscombineddiskspaceformasterandstandbymaster.

Hoverovereitherofthechartstoseethespaceused,free,andtotalingigabytesandasapercentageofthetotal.

GPSegmentsUsageHistoryTheGPSegmentsUsageHistorypanelpresentsachartofpercentageofdiskspaceinuseforthetimeperiodsetbythecontrolinthepanelheader.

Hoveroverthecharttoseethepercentagediskinuseonanygivenpoint.

StorageStatusTableTheStorageStatustableprovidescurrentdiskspaceusagemetricsforeachhostandbydatadirectorywithinhosts.

©CopyrightPivotalSoftwareInc,2013-2016 36 3.1.1

Page 37: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AdminTheAdminviewprovidestheabilitytomanageauthenticationandauthorizationforGreenplumCommandCenterConsoleandGreenplumDatabaseusers.

PermissionsViewtheGreenplumCommandCenterpermissionlevelforGreenplumDatabaseusers.Administratorscanchangeuser’spermissionlevels.

AuthenticationViewtheGreenplumDatabasehost-basedauthenticationfile( pg_hba.conf ).Administratorscanchangethefile.

©CopyrightPivotalSoftwareInc,2013-2016 37 3.1.1

Page 38: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

PermissionLevelsforGPCCAccessThePermissionsLevelsforGPCCAccessscreenallowsuserswithOperatorBasic,Operator,orAdminpermissiontoviewpermissionsforCommandCenterusers.UserswithAdminpermissioncansetpermissionsforallusers.

ViewingUserPermissionsInitially,allGreenplumDatabaseloginusersareincludedinthelistwiththeircurrentpermissionlevels.

Tofilterbyrolename,enterallorpartoftheuser’sdatabaserolenameintheRoleNamefield.Thefilterperformsasimplesubstringsearchanddisplaysuserswithmatchingrolenames.ClicktheRoleNamelabeltoreversethesearchorder.

Tofilterforuserswithaspecificpermissionlevel,choosethepermissionlevelfromthePermissionLevellist.

RoleNameandPermissionLevelfilterscanbeusedtogether.

Toresetthefilters,removealltextfromtheRoleNamefieldandchooseFilterby…fromthePermissionLevellist.

ChangingUserPermissionLevelsUserswithAdminpermissioncanchangepermissionlevels.

1. UsetheRoleNameandPermissionLevelfilterstodisplaytherolesyouwanttochange.

2. Checktheboxnexttoarolenametoselecttheuser,orchecktheboxintheheadingtoselectalldisplayedusers.

3. SelectthenewpermissionslevelforeachuserfromthelistinthePermissionLevelcolumn,orselectanewpermissionlevelforallselectedusersfromtheChangeSelectedto…list.

©CopyrightPivotalSoftwareInc,2013-2016 38 3.1.1

Page 39: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AuthenticationTheSystem>AuthenticationscreenallowsuserswithOperatorBasic,Operator,andAdminpermissiontoviewtheGreenplumDatabasehost-basedauthenticationfile, pg_hba.conf .

UserswithAdminpermissioncanadd,remove,change,andmoveentriesinthefile.TheCommandCenterUIvalidatesentriestoensurecorrectsyntax.Previousversionsofthefilearearchivedsothatyoucanrestoreanearlierversionorauditchanges.

SeeAuthenticationforanoverviewofuserauthenticationoptionsforGreenplumDatabaseandGreenplumCommandServer.

Seepg_hba.conffile inthePostgreSQLdocumentationforadetaileddescriptionofthecontentsofthe pg_hba.conf file.

ViewingtheHost-BasedAuthenticationFileChooseAdmin>AuthenticationtodisplaythecontentoftheGreenplumDatabase pg_hba.conf file.

The pg_hba.conf filecontainsalistofentriesthatspecifythecharacteristicsofdatabaseconnectionrequestsandauthenticationmethods.WhenGreenplumDatabasereceivesaconnectionrequestfromaclient,itcomparestherequesttoeachentryinthe pg_hba.conf entryinturnuntilamatchisfound.Therequestisauthenticatedusingthespecifiedauthenticationmethodand,ifsuccessful,theconnectionisaccepted.

EditingtheHost-BasedAuthenticationFileCommandCenteruserswiththeAdminpermissioncaneditthe pg_hba.conf file.Notethatanychangesyoumakearelostifyoumovetoanotherscreenbeforeyousavethem.

Tochangeanexistingentry,clickanywhereontheentry.EditthefieldsandclickSavetosaveyourchanges,orCanceltorevertchanges.

Tomoveanentryupordowninthelist,clickonthe symbol,dragthelinetothedesiredlocation,andrelease.

Toaddanewentrytotheendofthefile,clickAddNewEntryatthebottomofthescreen.EditthefieldsandclickSavetosaveyourchanges,orCanceltoabandonthenewentry.

Toaddanewentryafteranexistingentry,highlighttheexistingentryandclick .EditthefieldsandclickSavetosaveyourchanges,orCanceltoabandonthenewentry.

Tocopyanentry,selecttheentryandclick .Acopyoftheselectedentryisaddedbelowtheselectedentryanddisplayedforediting.EditthefieldsandclickSavetosaveyourchanges,orCanceltoabandonthecopy.

Toaddacommenttothefile,addanentrybyclickingAddNewEntry andthenchoose # fromthe Type list.

Totoggleanentrybetweenactiveandinactive,selectthelineandclicktheactive/inactivetogglecontroltotheright.Thisactionaddsorremovesacommentcharacter( # )atthebeginningoftheentry.

Toremoveanentry,highlightthelineandclick .Theentryisdisplayedwithstrikethroughtext.Youcanrestoretheentrybyhighlightingitandclickingundelete.TheentryispermanentlyremovedwhenyouclickSaveconfigandupdateGPDB.

Tofinishediting,clickSaveconfigandupdateGPDB.ThenclickSaveandUpdatetosaveyourchangesorclickCanceltoreturnwithyoureditsintact.

WhenyouselectSaveandUpdate,the pg_hba.conf fileissavedandrefreshedinGreenplumDatabase.Notethatexistingclientconnectionsareunaffected.

LoadingaPreviousVersionoftheHost-BasedAuthenticationFileWhenyousaveanewversionofthe pg_hba.conf file,acopyissavedintheGreenplumDatabase $MASTER_DATA_DIRECTORY/pg_hba_archive directoryaspg_hba.conf-<timestamp> .

Toviewanarchivedversionofthe pg_hba.conf file,clickLoadversions…andclickthetimestampfortheversiontodisplay.

Toreverttoapreviousversionofthefile,loadthepreviousversionandthenclickSaveconfigandupdateGPDB.TheconfigurationisrefreshedinGreenplumDatabaseandsavedasanewversioninthearchivedirectory.

or

©CopyrightPivotalSoftwareInc,2013-2016 39 3.1.1

Page 40: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

©CopyrightPivotalSoftwareInc,2013-2016 40 3.1.1

Page 41: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AdministeringGreenplumCommandCenterSystemadministrationinformationfortheGreenplumCommandCenter.

AbouttheCommandCenterInstallation

StartingandStoppingGreenplumCommandCenter

AdministeringCommandCenterAgents

AdministeringtheCommandCenterDatabase

AdministeringtheWebServer

ConfiguringGreenplumCommandCenter

EnablingMulti-ClusterSupport

SecuringaGreenplumCommandCenterConsoleInstance

©CopyrightPivotalSoftwareInc,2013-2016 41 3.1.1

Page 42: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

StartingandStoppingGreenplumCommandCenterGreenplumCommandCenterincludesthecommandcenterconsoleandthecommandcenteragents.

StartingandStoppingCommandCenterAgentsWhenevertheGreenplumDatabaseserverconfigurationparameter gp_enable_gpperfmon isenabledinthemaster postgresql.conf file,theCommandCenteragentswillrunandcollectdata.TheseagentsareautomaticallystoppedandstartedtogetherwiththeGreenplumDatabaseinstance.

TodisabletheCommandCenterdatacollectionagents,youmustdisablethe gp_enable_gpperfmon parameter,andrestarttheGreenplumDatabaseinstance.

StartingandStoppingCommandCenterConsoleUsethefollowing gpcmdr commandstostart,stopandrestartGreenplumCommandCenterConsoleinstances:

$gpcmdr--start["instancename"]

$gpcmdr--stop["instancename"]

$gpcmdr--restart["instancename"]

Ifyoudonotspecifyaninstancename,allinstancesarestarted,stopped,orrestartedatonce.Youcancheckthestatusofinstancesusing:

$gpcmdr--status["instancename"]

©CopyrightPivotalSoftwareInc,2013-2016 42 3.1.1

Page 43: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AdministeringCommandCenterAgentsThistopicdescribesbasicagentadministrationtasks,includingaddinghostsandviewingagentlogfiles.

AddingandRemovingHostsSegmentagentsonnewhostsaredetectedautomaticallybythemasteragent.Whenever gp_enable_gpperfmon isenabledonthemaster,themastermonitoragentautomaticallydetects,starts,andbeginsharvestingdatafromnewsegmentagents.

Toverifytheadditionofanewmonitoredhost,youcancheckforthenewhostnameintheGreenplumCommandCenterConsoleSystemMetricsview.Alternately,youcanquerythe system_now tablefortherowcontainingcurrentmetricsforeachhost.Forexample:

#SELECT*FROMsystem_nowWHEREhostname='new_hostname';

ViewingandMaintainingMasterAgentLogFilesLogmessagesforthemasteragentarewrittentothefollowingfilebydefault:

$MASTER_DATA_DIRECTORY/gpperfmon/logs/gpmmon.log

Tochangethelogfilelocation,editthe log_location parameterin gpperfmon.conf .

Onthesegmenthosts,agentlogmessagesarewrittentoa gpsmon.log fileinthesegmentinstance’sdatadirectory.Forahostwithmultiplesegments,theagentlogfileislocatedinthedatadirectoryofthefirstsegment,aslistedinthe gp_configuration tablebydbid.Ifthesegmentagentisunabletologintothisdirectory,itwilllogmessagestothehomedirectoryoftheuserrunningCommandCenter(typically gpadmin ).

ConfiguringLogFileRolloverAthigherlogginglevels,thesizeofthelogfilesmaygrowdramatically.Topreventthelogfilesfromgrowingtoexcessivesize,youcanaddanoptionallogrolloverparameterto gpperfmon.conf .Thevalueofthisparameterismeasuredinbytes.Forexample:

max_log_size=10485760

Withthissetting,thelogfileswillgrowto10MBbeforethesystemrollsoverthelogfile.Thetimestampisaddedtothelogfilenamewhenitisrolledover.Administratorsmustperiodicallycleanoutoldlogfilesthatarenolongerneeded.

©CopyrightPivotalSoftwareInc,2013-2016 43 3.1.1

Page 44: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AdministeringtheCommandCenterDatabaseDatacollectedbyCommandCenteragentsisstoredinadedicateddatabasecalledgpperfmonwithintheGreenplumDatabaseinstance.Thisdatabaserequiresthetypicaldatabasemaintenancetasks,suchascleanupofoldhistoricaldataandperiodic ANALYZE .

SeetheCommandCenterDatabaseReferencesectionforareferenceofthetablesandviewsinthegpperfmondatabase.

ConnectingtotheCommandCenterDatabaseDatabaseadministratorscanconnectdirectlytotheCommandCenterdatabase( gpperfmon )usinganyGreenplumDatabase-compatibleclientprogram(suchas psql ).Forexample:

$psql-dgpperfmon-hmaster_host-p5432-Ugpadmin

BackingUpandRestoringtheCommandCenterDatabaseThehistorytablesoftheCommandCenterdatabase( gpperfmon )canbebackedupandrestoredusingtheGreenplumDatabaseparallelbackupandrestoreutilities( gpcrondump , gpdbrestore ).SeetheGreenplumDatabaseUtilityGuideformoreinformation.

BecausetheCommandCenterdatabasehasalownumberoftables,youmayprefertodeviseabackupplanusingthetable-levelbackupfeaturesofgp_dump .Forexample,youcancreatescriptstorun gp_dump tobackupthemonthlypartitionsofthehistoricaldatatablesonamonthlyschedule.Alternately,youcanbackupyourCommandCenterdatabaseatthedatabaselevel.

MaintainingtheHistoricalDataTablesAllofthe *_history tablesstoredintheCommandCenterdatabase( gpperfmon )arepartitionedintomonthlypartitions.AJanuary2010partitioniscreatedatinstallationtimeasatemplatepartition(itcanbedeletedoncesomecurrentpartitionsarecreated).TheCommandCenteragentsautomaticallycreatenewpartitionsintwomonthincrementsasneeded.AdministratorsmustperiodicallydroppartitionsforthemonthsthatarenolongerneededinordertomaintainthesizeoftheCommandCenterdatabase.

SeetheGreenplumDatabaseAdministratorGuideformoreinformationondroppingpartitionsofapartitionedtable.

©CopyrightPivotalSoftwareInc,2013-2016 44 3.1.1

Page 45: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AdministeringtheWebServerThegpmonwswebserverisinstalledinthe www directoryofyourGreenplumCommandCenterinstallation.

ConfiguringtheWebServerThewebserverconfigurationfileisstoredin $GPPERFMONHOME/instances/instance_name/webserver/conf/app.conf .Someoftheparametersinthisconfigurationfilearesetbythe gpcmdr setuputility,includingthewebserverportandSSLoptions.SeetheWebServerParameterssectionofConfigurationFileReferenceforadescriptionoftheparametersinthisfile.

ViewingandMaintainingWebServerLogFilesWebserveraccessanderrorlogmessagesarewrittento $GPPERFMONHOME/instances/<instance_name>/webserver/logs/gpmonws.log .

IfyouexperienceerrorsviewingtheGreenplumCommandCenterConsole,refertothisfileformoreinformation.

Topreventthewebserverlogfromgrowingtoexcessivesize,youcansetuplogfilerotationusing logrotate or cronolog .

©CopyrightPivotalSoftwareInc,2013-2016 45 3.1.1

Page 46: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ConfiguringGreenplumCommandCenterConfigurationparametersforGreenplumCommandCenterarestoredintheAgentandConsoleconfigurationfiles.

AgentConfigurationChangestothesefilesrequirearestartoftheGreenplumDatabaseinstance( gpstop-

r).

$MASTER_DATA_DIRECTORY/gpperfmon/conf/gpperfmon.conf

$MASTER_DATA_DIRECTORY/postgresql.conf

ConsoleConfigurationChangestothesefilesrequirearestartofCommandCenterConsole( gpcmdr--restart ).

$GPPERFMONHOME/instances/<instance_name>/conf/clusters.conf

$GPPERFMONHOME/instances/<instance_name>/webserver/conf/app.conf

SeetheConfigurationFileReferencesectionforadescriptionoftheconfigurationparametersinthesefiles.

Youshouldnotneedtomanuallyeditanyofthefiles.RunningtheCommandCentersetuputilitywillmakeallthenecessarymodificationstotheseconfigurationfiles.

©CopyrightPivotalSoftwareInc,2013-2016 46 3.1.1

Page 47: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

EnablingMulti-ClusterSupportMulti-clusterfunctionalityallowsyoutoviewthestatusofmultipleGreenplumDatabaseclustersatonetimeintheCommandCenteruserinterface.Theclusterscanbeorganizedintogroups.

Typically,oneGreenplumclusterisdesignatedthemastercluster;itsCommandCenterinstancehoststhemulti-clusterviewforallCommandCenter-managedclusters.

SeeMonitoringMultipleGreenplumDatabaseClustersforinformationaboutaccessingthemulti-clusterview.

SettingUpMultipleClustersMulti-clustersupportisenabledwithamulti-clusterconfigurationfile.ThereisatemplateforthisconfigurationfileintheinstancedirectoryofeachCommandCenterinstanceatthefollowinglocation:

$GPCCHOME/instances/<instance_name>/conf/clusters.conf

Locatethe clusters.conf templateontheCommandCenterinstanceyouwanttoidentifyasthemasterinstance.Thiswillbethewebserverthathoststhemulti-clusterwebpage.

Theconfigurationfileconsistsofthefollowingvaluesseparatedbycolons:

SERVER:HOST:PORT:TABGROUP:AUTOLOGIN:SSL:ACCESS

Forexample:

Miracle:www.example.com:28080:Production:True:false:gpdb_role,accounting_roleDeforest:192.51.100.186:28080:Development:False:falseGrandalpha:grandalpha:32020:Development:False:false

Allfieldsexceptthelast,ACCESS,arerequired.

SERVERTheservervalueisaprimarykey,usedtouniquelyidentifyeachGreenplumDatabasecluster.

Thenamemaynotcontainspecialcharacters,otherthanthespacecharacter,underscore( _ ),orhyphen( - ).

CommandCenterthrowsanerrorifthereareanyentrieswiththesameprimarykey.

HOSTThisisthehostnameorIPaddressforthecluster’sCommandCenterUI.

PORTTheCommandCenterportnumber.

TABGROUPThisfieldisusedtodivideGreenplumDatabaseclustersintocategories;forexample,Testing,Production,andDeployment.

AUTOLOGINThisfieldenablesautomaticlogintotheclusterfromthemulti-clusterview.Whenautomaticloginisenabled,clickingthecluster’shealthchartonthemulti-clusterpageloadsthecluster’sCommandCenterUIinanewbrowserwindow.

TheAUTOLOGINfieldisatrueorfalsevalue.Itisnotcase-sensitive.

SSLThisfieldindicateswhetherSSLisenabledforthehost.Ittakesatrueorfalsevalueandisnotcase-sensitive.Anyothervalueisanerror,whichwillbeshownintheUI.

Important:AllhostsmusthavethesameSSLconfiguration.SSLmustbeenabledordisabledforallhosts.

ACCESSThisoptionalfieldcontainsacomma-separatedlistofdatabaserolesthatcanseetheMultipleGPDBClustersview.Ifthisfieldisempty,alluserscanseetheview.

©CopyrightPivotalSoftwareInc,2013-2016 47 3.1.1

Page 48: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

©CopyrightPivotalSoftwareInc,2013-2016 48 3.1.1

Page 49: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

SecuringaGreenplumCommandCenterConsoleInstanceAGreenplumCommandCenterConsoleinstancecanbesecuredbyencryptingnetworktrafficbetweenthewebserverandusers’browsers,authenticatingCommandCenterusers,andmanagingusers’permissionstoaccessCommandCenterfeatures.

SSL/TLSEncryptionGreenplumCommandCentersupportsSSL/TLSencryptiontosecureconnectionsbetweenbrowsersandtheCommandCenterwebserver.ToenableSSL,youshouldhaveasignedcertificatefortheCommandCenterwebserverinplacewhenyoucreatetheCommandCenterinstance.

PlaceyourcertificateontheserverwhereCommandCenterisinstalled,forexampleinthe /etc/ssl/certs directoryoftheGreenplummasterhost.YouimportthecertificatewhenyoucreateaCommandCenterinstancewiththe gpcmdr--

setupcommand.Thelocationsofthecertificateandprivatekeyfiles

aresavedinthe $GPPERFMONHOME/instances/<instance_name>/webserver/conf/app.conf configurationfileforthecommandcenterinstance.SeeCommandCenterConsoleParametersfordetails.

Youcanrequestacertificatefromyourorganization’sinternalcertificateauthorityoracommercialcertificateauthority,oryoucanuseaself-signedcertificateyoucreateyourselfwithacryptographysuitesuchasOpenSSL.Ifyoucreateaself-signedcertificate,notethatclientswillhavetooverrideasecuritywarningwhentheyfirstconnecttotheCommandCenterwebserver.

AuthenticationOptionsUsersloggingintoGreenplumCommandCenterareauthenticatedwiththeGreenplumDatabasehost-basedauthenticationsystem.Userscanentercredentialsasausernameandpasswordor,ifKerberosauthenticationisconfigured,byauthenticatingwithKerberosontheirworkstationbeforebrowsingtotheCommandCenterwebserver.

DatabaseusersmustfirstbeaddedtotheGreenplumDatabasebyusingcommandssuchas CREATEROLE or CREATEUSER .The LOGIN privilegeisrequired.Thisexamplecreatesaloginuserwithanencryptedpassword:

CREATEROLEcc_userWITHLOGINENCRYPTEDPASSWORD'changeme';

The pg_hba.conf configurationfiledetermineshowauthenticationwillproceed.Thisfilecontainsalistofentriesthatarecomparedtoattributesoftheuser’sconnectionrequest,includingthetypeofconnection,networklocationoftheoriginatinghost,databasename,andloginusername.Whenamatchisfound,theauthenticationmethodspecifiedintheentryisapplied.

The pg_hba.conf filecanbeviewedbyOperatorsandeditedbyAdminsintheCommandCenterconsoleontheAdmin>Authenticationpage.

Usersconfiguredwithlocal trust authenticationaredeniedaccesstoCommandCenterbecausethismethodisnotsecure.Usingremote trustauthenticationisdiscouragedforthesamereason.

The md5 and password authenticationmethodsauthenticatetheusernameandpasswordwiththeGreenplumDatabase pg_roles systemtable.Themd5 methodrequiresthepasswordtobeMD5-encodedwhensentoverthenetwork,soitispreferredoverthe password method,whichsendsthepasswordincleartext.

The ldap authenticationmethodauthenticatestheusernameandpasswordwithanLDAPserver.TheLDAPserverandparametersarespecifiedintheoptionsfieldofthe pg_hba.conf entry.SeethePostgreSQLLDAPauthentication documentationfortheformatoftheLDAPoptions.

The gss authenticationmethodisusedforKerberosauthentication.TouseKerberoswithCommandCenter,KerberosauthenticationmustbeenabledfortheGreenplumDatabasesystemandtheCommandCenterinstancemustalsobeconfigured.UsersauthenticatewiththeKerberosKDContheirworkstations(using kinit ,forexample)beforeconnectingtotheCommandCenterwebserver.TherolenameinCommandCenteristheuser’sKerberosprincipalname.

FordetailsaboutsettingupKerberosauthentication,seeEnablingKerberosAuthenticationwithGreenplumCommandCenter.

SeethePostgreSQLAuthenticationmethods documentationforadditionaldetailsoftheauthenticationoptions.

AuthorizationCommandCentermanagespermissionlevelsusingGreenplumDatabaserolesandgroups.TheBasic,OperatorBasic,andOperatorpermissionlevels

©CopyrightPivotalSoftwareInc,2013-2016 49 3.1.1

Page 50: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

correspondtothe gpcc_basic , gpcc_operator_basic ,and gpcc_operator grouprolesinthedatabase.TheAdminpermissionlevelisconferredtorolesthathavethe SUPERUSER privilege.Auserwhohasnotbeenaddedtoanyofthegroupsanddoesnothave SUPERUSER privilegehasthemostrestrictivepermissionlevel,SelfOnly.

GreenplumDatabasesuperuserscanmanagepermissionlevelsontheCommandCenterAdmin>Permissionspage.Superuserscanalsodirectlyassignusersrolesinthedatabasebyusingthe ALTERUSER , ALTERGROUP ,andrelatedcommandstoaddorremoveusersfromgroupsandaddorremovethe SUPERUSER privilege.Ifaroleisconfiguredformorethanonepermissionlevel,CommandCenterusesthehighestpermissionlevel.

CommandCenterusershavethefollowingcapabilities,accordingtotheirpermissionlevels:

SelfOnlyUserscanviewmetricsandviewandcanceltheirownqueries.

AnyGreenplumDatabaseusersuccessfullyauthenticatedthroughtheGreenplumDatabaseauthenticationsystemcanaccessGreenplumCommandCenterwithSelfOnlypermission.Higherpermissionlevelsarerequiredtoviewandcancelother’squeriesandtoaccesstheSystemandAdminControlCenterscreens.

BasicAllowsuserstoviewmetrics,viewallqueries,andcanceltheirownqueries.

UserswithBasicpermissionaremembersoftheGreenplumDatabase gpcc_basic group.

OperatorBasicAllowsuserstoviewmetrics,viewtheirownandothers’queries,canceltheirownqueries,andviewtheSystemandAdminscreens.

UserswithOperatorRead-onlypermissionaremembersoftheGreenplumDatabase gpcc_operator_basic group.

OperatorAllowsuserstoviewtheirownandothers’queries,canceltheirownandother’squeries,andviewtheSystemandAdminscreens.

UserswithOperatorpermissionaremembersoftheGreenplumDatabase gpcc_operator group.

AdminAllowsusersaccesstoallviewsandcapabilitiesintheCommandCenter.

GreenplumDatabaseuserswiththe SUPERUSER privilegeinGreenplumDatabasehaveSuperuserpermissionsinCommandCenter.

©CopyrightPivotalSoftwareInc,2013-2016 50 3.1.1

Page 51: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ConfiguringAuthenticationfortheCommandCenterConsoleGreenplumCommandCenterusersareGreenplumDatabaseusers,authenticatedusingthestandardGreenplumDatabasehost-basedauthenticationsystem.Whenauthenticationisproperlyconfigured,ausercanusethesamecredentialstologintoadatabasewithadatabaseclientsuchas psql andintotheCommandCenterwebinterfacewithabrowser.

TocreateanewCommandCenteruser,firstyouhavetocreateaGreenplumDatabaseuser,thenedittheGreenplumhost-basedauthenticationconfigurationfile( pg_hba.conf )togivethatuseraccesstoCommandCenter.

AnyGreenplumDatabaseuserwhocanauthenticateviathe pg_hba.conf filecanlogintoGreenplumCommandCenterandvieworcanceltheirownqueriesandviewmetricsscreens.Auser’sCommandCenterpermissionleveldeterminesifadditionalCommandCenterfeaturesareaccessible.SeeAuthorizationforinformationaboutpermissions.

ThefollowingarestepstocreatenewCommandCenterusersinaninteractive psql session.Withtheexceptionofthe CREATEROLE commandtocreateanewdatabaseuser,allofthesestepscanbeperformedintheCommandCenterontheAdmin>PermissionsorAdmin>Authorizationscreens.

SeetheGreenplumDatabaseAdministratorGuideformoredetailedinformationaboutcreatingdatabaseusersandroles.

1. Loginas gpadmin onthemasterhost.

2. Start psql :

$psql

3. Enterthe CREATEROLE commandtocreateauser:

#CREATEROLEcc_userWITHLOGINENCRYPTEDPASSWORD'changeme';

TocreateanAdminuser-arolewithsuperuserprivilegesinthedatabaseandGreenplumCommandCenter:

#CREATEROLEcc_adminWITHLOGINENCRYPTEDPASSWORD'changeme'SUPERUSERCREATEDB;

4. ForusersotherthanAdmin,setthepermissionlevelbyaddingtheusertoaCommandCentergrouprole:TocreateaBasicuser:addtheusertothe gpcc_basic role:

#GRANTgpcc_basicTOcc_user;

TocreateanOperatorBasicuser-addtheusertothe gpcc_operator_basic role:

#GRANTgpcc_operator_basicTOcc_user;

TocreateanOperatoruser-addtheusertothe gpcc_operator role:

#GRANTgpcc_operatorTOcc_user;

5. Grantpermissionstoagroupbygrantingtheroletothegroup:

#CREATEROLEcc_users;#GRANTcc_userstocc_user;#GRANTgpcc_operatortocc_users;

6. Verifythatroleswerecreatedsuccessfullyusingthefollowingcommand:

#\du

Thenewusersyoucreatedarereturnedalongwiththeattributesyouspecified.

7. Editthe pg_hba.conf filetogivenewusersaccesstodatabasesandtheCommandCenter.Openthefileinaneditor:

$vi$MASTER_DATA_DIRECTORY/pg_hba.conf

8. ScrolltothebottomofthefileandinsertthefollowinglinestogivethenewusersaccessfromanyIPaddressusingpasswordauthentication:

©CopyrightPivotalSoftwareInc,2013-2016 51 3.1.1

Page 52: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

hostgpperfmoncc_user127.0.0.1/28md5hostgpperfmoncc_admin127.0.0.1/28md5

Listadditionaldatabasestheuserscanaccessafter gpperfmon ,orreplace gpperfmon with all toallowtheuserstoaccessanydatabase.Note:IfyousubsequentlyhaveissuesloggingintoCommandCenteritmaybeduetoyourspecificenvironment;checkthe$GPPERFMON/instances/instance_name/logs/gpmonws.log logfileforauthenticationerrors.Editthe pg_hba.conf filebasedontheerrormessageandyourspecificenvironment.

9. Savethefileandexittheeditor.

10. EnterthefollowingcommandtoreloadGreenplumDatabaseprocesses.

#gpstop-u

©CopyrightPivotalSoftwareInc,2013-2016 52 3.1.1

Page 53: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

EnablingAuthenticationwithKerberosIfyouhaveenabledKerberosauthenticationforGreenplumDatabase,youcansetupGreenplumCommandCentertoacceptconnectionsfromKerberos-authenticatedusers.

GreenplumDatabaseandCommandCenterincludesupportfortheGenericSecurityServiceApplicationsProgramInterface(GSS-API)standard.Arelatedstandard,SimpleandProtectedGSS-APINegotiationMechanism(SPNEGO),describestheprotocolGSS-APIclientsandserversusetoagreeonthemethodofauthentication.

WithaSPNEGO-compliantwebapplicationsuchasCommandCenter,theclientandserveragreeontheauthenticationmethodontheclient’sinitialHTTPrequest.IfKerberosauthenticationisnotsupportedonbothendsoftheconnectiontheserverfallsbacktobasicauthentication,anddisplaysaloginformrequestingausernameandpassword.IfauserhasauthenticatedontheworkstationwithKerberosandhasavalidticketgrantingticket,thewebbrowserofferstheuser’scredentialtotheCommandCenterwebserver.AKerberos-enabledCommandCenterwebserverisconfiguredtohandletheauthenticateduser’sconnectionrequestinoneofthreemodes,calledstrict,normal,orgpmon-only.

StrictCommandCenterhasaKerberoskeytabfilecontainingtheCommandCenterserviceprincipalandaprincipalforeveryCommandCenteruser.Iftheprincipalintheclient’sconnectionrequestisinthekeytabfile,thewebservergrantstheclientaccessandthewebserverconnectstoGreenplumDatabaseusingtheclient’sprincipalname.Iftheclient’sprincipalisnotinthekeytabfile,theserverfallsbacktobasicauthentication.

NormalTheCommandCenterKerberoskeytabfilecontainstheCommandCenterprincipalandmaycontainprincipalsforCommandCenterusers.Iftheprincipalintheclient’sconnectionrequestisinCommandCenter’skeytabfile,itusestheclient’sprincipalfordatabaseconnections.Otherwise,CommandCenterusesthe gpmon userfordatabaseconnections.

gpmon-onlyTheCommandCenterusesthe gpmon databaseroleforallGreenplumDatabaseconnections.NoclientprincipalsareneededintheCommandCenter’skeytabfile.

IfyouhavesetupKerberosauthenticationforGreenplumDatabase,mostoftheconfigurationrequiredtoenableCommandCenterKerberosauthenticationhasbeendone.TheCommandCenterKerberosconfigurationbuildsupontheGreenplumDatabaseKerberossetup.

KerberosauthenticationcanbeenabledbyrespondingtopromptswhenyousetupanewCommandCenterinstancewiththe gpcmdr--setup

command,or

youcanusethe gpcmdr--krbenable<instance-name>

commandtoenableKerberosforanexistingCommandCenterinstance.

BeforeYouBeginKerberosauthenticationmustbeenabledforGreenplumDatabase.SeeUsingKerberosAuthentication forinstructions.Makesurethefollowingprerequisitesaremetbeforeyoucontinue:

The krb5-workstation packageandassociatedlibraries( libkrb5* )mustbeinstalledontheGreenplummasterhostandeachclientworkstation.

ThedateandtimeontheGreenplummasterhostandallclientworkstationsmustbesynchronizedwiththeKDC.

The krb5.conf configurationfilemustbethesameontheKDChost,theGreenplummasterhost,andclientworkstations.

TheKDCdatabasemusthaveaserviceprincipalforGreenplumDatabase.ThedefaultservicenameforGreenplumDatabaseispostgres/<master-host>@<realm> .Youcanchooseaservicenameotherthan postgres ,butitmustmatchthevalueofthe krb_srvnameparameterinthe $MASTER_DATA_DIRECTORY/postgresql.conf file.

AkeyfilefilewiththeGreenplumDatabaseprincipalmustbeinstalledontheGreenplummasterhostandidentifiedbythekrb_server_keyfileparameterinthe $MASTER_DATA_DIRECTORY/postgresql.conf file.

EachclientworkstationmusthaveakeytabfilecontainingtheirKerberosprincipal, <username>@<realm> .

AddCommandCenterPrincipalstotheKDCDatabaseBeforeyouconfigureaCommandCenterinstanceforKerberosauthentication,youmustcreatetherequiredKerberosprincipals.AlloftheprincipalsusedwithCommandCenterarecreatedintheGreenplumDatabaseKerberosrealm.CommandCenterusersusethesameKerberosprincipaltologintoCommandCenterandGreenplumDatabase.

CommandCenterServicePrincipal

©CopyrightPivotalSoftwareInc,2013-2016 53 3.1.1

Page 54: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

AserviceprincipalisneededfortheCommandCenterwebserver.Thisprincipalhastheformat HTTP/<host>@<realm> .Forexample,ifusersaccessCommandCenterattheURL http://mdw.example.com:28080 ,the <host> partoftheservicekeyis mdw.example.com andthe <realm> partistheGreenplumDatabaseKerberosrealm,forexample GPDB-KRB.EXAMPLE.COM .

NotethatKerberosauthenticationonlyworksifCommandCenterusersenterthehostinthesameformatspecifiedintheKerberosserviceprincipal.IftheprincipalspecifiestheFQDN,forexample,usingthehost’sIPaddressinthebrowserURLwillnotwork;thewebserverwillfallbacktobasicauthentication,presentingaloginscreen.

GreenplumDatabasegpmonUser

CommandCenterusesthe gpmon Greenplumroletoaccessthe gpperfmon database,whichcontainsdatapresentedintheCommandCenterUI.

Youcanchoosetoauthenticatethe gpmon userwithKerberosorwithbasicauthentication.TouseKerberos,youmustcreateaprincipalforthegpmon user.

IfyouchoosetousebasicauthenticationyoudonotneedaKerberosprincipalforthe gpmon user.The gpmon userwillauthenticatewithGreenplumDatabaseusingthepasswordsavedinthe ~gpadmin/.pgpass fileonthehostrunningtheCommandCenterinstance.SeeChangingthegpmonPasswordforinstructionstomanagethe gpmon password.

CommandCenterUsers

AddKerberosprincipalsforanyCommandCenteruserswhodonotalreadyhaveprincipalsintheKDCforGreenplumDatabase.

AddingKerberosPrincipalsToaddtherequiredprincipals,performthefollowingstepsasrootontheKDCserver.

1. Start kadmin.local .

kadmin.local

2. AddaprincipalfortheCommandCenterwebservice.Besuretospecifythe <gpcc-host> inthesameformatthatusersshouldenterthehostintheirbrowsers.

kadmin.local:addprincHTTP/<gpcc-host>@<realm>

3. Ifyouwantthe gpmon databaseusertouseKerberosauthentication,adda gpmon principal.

kadmin.local:addprincgpmon@<realm>

4. AddprincipalsforanynewCommandCenterusers.

kadmin.local:addprinccc_user1@<realm>

RepeatforeachnewCommandCenteruser.

5. Enter quit toexit kadmin.local .

SetUpKeytabFilesAfteryouhavecreatedalloftheKerberosprincipalsneeded,youcreateanddistributekeytabfiles.KeytabfilescontainKerberosprincipalsandencryptedkeysbasedontheprincipals’Kerberospasswords.KeytabfilesareneededforGreenplumDatabase,theCommandCenterinstance,andeachCommandCenterandDatabaseuser.

TheCommandCenterinstanceisusuallyinstalledontheGreenplummasterand,whenthisistrue,asinglekeyfilefilecanbesharedbyGreenplumDatabaseandtheCommandCenterinstance.RunningCommandCenterontheGreenplummasterisrecommended,sinceitconfinesauthenticationwiththedatabasetoasinglehost.

IfyouinstalltheCommandCenterinstanceonahostotherthantheGreenplummaster,youwillneedtocreateaseparatekeyfilefile.

YoumustalsocreateakeyfilefileforeachGreenplumDatabaseorCommandCenterusercontainingjusttheuser’sprincipal.Thiskeyfilefileisinstalledontheuser’sworkstationtoenabletheusertoauthenticatetoKerberos.

©CopyrightPivotalSoftwareInc,2013-2016 54 3.1.1

Page 55: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CommandCenterInstanceontheGreenplumMasterHostIftheGreenplumCommandCenterwebserverisrunningontheGreenplumDatabasemasterhost,CommandCentercansharetheGreenplumDatabasekeyfilefile.Youneedtocreateakeyfilefilethatcontainsthefollowingprincipals:

Servicekeyforthe postgres processontheGreenplumDatabasemasterhost,forexample postgres/[email protected] .

ServicekeycreatedforCommandCenterintheprevioussection,forexample HTTP/[email protected].

AprincipalforeveryKerberos-authenticatedGreenplumDatabaseorCommandCenteruser.

AllservicekeysandprincipalsshouldbeintheGreenplumDatabaserealm.

TocreateakeytabfileforGreenplumDatabaseandCommandCenter,performperformthefollowingstepsasrootontheKDCserver.

1. Start kadmin.local .

kadmin.local

2. CreateakeytabfileandaddtheGreeplumDatabaseservicekey,thecommandcenterservicekey,andalldatabaseandCommandCenterusers.

kadmin.local:ktadd-kgpdb-kerberos.keytabpostgres/[email protected]/[email protected]

Youcanenteroneormoreprincipalswitheach ktadd command.Youcanspecifyawildcardusingthe -glob option.Forexamplethiscommandaddsallprincipalsinthe GPDB.EXAMPLE.COM realm,includingserviceprincipalsandadminusers.

kadmin.local:ktadd-kgpdb-kerberos.keytab-glob*@GPDB.EXAMPLE.COM

3. Enter quit toexit kadmin.local .

4. CopythekeyfileyoucreatedtotheGreenplumDatabasemasterhost,replacingtheoldkeytabfile.Thelocationofthefileisgivenbythekrb_server_keyfile parameterinthe $MASTER_DATA_FILE/postgresql.conf file.Setthepermissionsonthefilesothatitcanbereadonlybythe gpadmin

user.

5. UpdateanyentriesrequiredfornewGreenplumDatabaseprincipalsinthe pg_hba.conf fileand pg_ident.conf files.SeeUpdatetheGreenplumDatabasepg_hba.confFilefordetails.

CommandCenterInstanceonaSeparateHostIftheCommandCenterwebserverisonadifferenthostthantheGreenplumDatabasemaster,youneedseparatekeytabfilesforGreenplumDatabaseandCommandCenter.ThekeytabfileforGreenplumDatabasemaynotrequireanyupdates,butyouwillneedtocreateakeytabfileforCommandCenter.

TheGreenplumDatabasekeytabfilemustcontaintheGreenplumDatabaseservicekeyandallprincipalsforuserswithdatabaseaccess.

TheCommandCenterkeytabfilecontainstheCommandCenterservicekeyandprincipalsforusersthathaveCommandCenteraccess.UserswithCommandCenteraccessmustalsohaveGreenplumDatabaseaccess,souserprincipalsintheCommandCenterkeytabfilemustalsobeintheGreenplumDatabasekeytabfile.

UpdatetheGreenplumDatabasekeyfileifyoucreatednewdatabaserolesandprincipalsforCommandCenter.Forexample,ifyouwanttouseKerberosauthenticationforthe gpmon user,youmustcreateaprincipalandaddittoboththeGreenplumDatabaseandCommandCenterkeytabfiles.

TocreatethekeytabfileforCommandCenter,performthefollowingstepsasrootontheKDChost.

1. Start kadmin.local .

kadmin.local

2. CreateakeytabfileandaddtheCommandCenterservicekey.

kadmin.local:ktadd-kgpcc-kerberos.keytabHTTP/[email protected]

3. Ifyouwanttoauthenticatethe gpmon userwithKerberos,addthe gpmon principal.

kadmin.local:[email protected]

©CopyrightPivotalSoftwareInc,2013-2016 55 3.1.1

Page 56: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

4. AddprincipalsforallCommandCenterusers:

kadmin.local:[email protected][email protected]

Youcanenteroneormoreprincipalswitheach ktadd command.

5. Enter quit toexit kadmin.local .

6. CopythekeyfileyoucreatedtothethehostrunningCommandCenter,forexample:

$scpgpcc-kerberos.keytabgpadmin@<host-name>:/home/gpadmin

7. Updateanyentriesrequiredfornewprincipalsinthe pg_hba.conf fileand pg_ident.conf filesontheGreenplummaster.SeeUpdatetheGreenplumDatabasepg_hba.confFile.

UpdatetheGreenplumDatabasepg_hba.confFileTheGreenplumDatabase $MASTER_DATA_DIRECTORY/pg_hba.conf configurationfiledetermineswhichauthenticationmethodstousetoallowdatabaseaccess.

IfyoucreatednewCommandCenterusers,youmayneedtoaddanentrytoallowaccessviaCommandCenter.Theentryforanindividualuserhasthisformat:

hostdatabase<user-name><gpccCIDR>gss[options]

Authenticationforthe gpmon userneedstobesetupinthe pg_hba.conf fileinoneofthefollowingways.

Basicauthentication

The /home/gpadmin/.gpass filecontainsthepasswordfor gpmon touse.SeeChangingthegpmonPasswordfordetails.Anentryinthe pg_hba.conf filespecifiesthemd5authenticationmethodfor gpmon :

localallgpmonmd5

Trustauthentication

OntheGreenplumDatabasehostonly,the gpmon usercanaccessdatabaseswithoutauthentication:

localallgpmontrust

The /home/gpadmin/.pgpass fileisnotneeded.

Kerberosauthentication

AKerberosprincipalhasbeencreatedforthe gpmon userandaddedtotheGreenplumDatabaseandCommandCenterkeytabfiles.

hostallgpmon<gpccCIDR>]gss[options]

Removeanyexistingrejectrulesfor gpmon :

hostallgpmon<auth-method>reject

SeeUsingKerberosAuthentication formoreinformationaboutthe pg_hba.conf file.

EnableKerberosfortheCommandCenterInstanceSetuptheCommandCenterinstancetousetheCommandCenterkeytabfileyoucreated.

©CopyrightPivotalSoftwareInc,2013-2016 56 3.1.1

Page 57: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

IfyouarecreatinganewCommandCenterinstancewiththe gpcmdr--setup

command,answer Y totheprompt Enablekerberosloginforthisintance?

,and

entertheCommandCenterhostnameandpathtothekeytabfileattheprompts.SeeCreatetheGreenplumCommandCenterInstance forcompleteinstructions.

IfyouareaddingKerberosauthenticationtoanexistingCommandCenterinstance,usethe gpcmdr--krbenable<instance-name>

command.Forexample,if

yourCommandCenterinstanceisnamed my-gpcc enterthiscommand:

$gpcmdr--krbenablemy-gpcc

EntertheCommandCenterhostnameandpathtothekeytabfileattheprompts.SeethegpcmdrReferenceformoreinformation.

AuthenticatingWithKerberosontheClientWorkstationTouseKerberosCommandCenterauthentication,theusermusthaveauthenticatedwithKerberosusingthe kinit command-linetool.

TheuserthenaccessestheCommandCenterwebserverwithaURLcontainingthehostnameintheformatspecifiedintheCommandCenterserviceprincipalandtheportnumber,forexample http://gpcc.example.com:28080 .

ThewebbrowsermustbeconfiguredtousetheSPNEGOprotocolsothatitofferstheuser’sKerberosprincipaltothewebbrowser.Themethodforconfiguringwebbrowsersvarieswithdifferentbrowsersandoperatingsystems.SearchonlinetofindinstructionstosetupyourbrowserandOS.

©CopyrightPivotalSoftwareInc,2013-2016 57 3.1.1

Page 58: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

SecuringthegpmonDatabaseUserTheGreenplumDatabase gpmon userisasuperuserroleusedtomanagethe gpperfmon database.The gpperfmon_install utility,whichmustberunoncebeforeyoucancreateaCommandCenterConsoleinstance,createsthe gpmon role.

GreenplumDatabaseusesthe gpmon roletoupdatethe gpperfmon databasewithdatacollectedbyagentsrunningonthesegmenthosts.TheCommandCenterwebserverusesthe gpmon roletoconnecttothe gpperfmon databaseaswellasdatabasesmonitoredbytheCommandCenterinstance.

When gppermon_install createsthe gpmon role,itpromptsforapassword,whichitthenaddstothe .pgpass fileinthe gpadmin user’shomedirectory.Theentryinthe .pgpass fileissimilartothefollowing:

*:5432:gpperfmon:gpmon:changeme

SeeThePasswordFile inthePostgreSQLdocumentationfordetailsaboutthe .pgpass file.

Inthe $MASTER_DATA_DIRECTORY/pg_hba.conf authenticationfile, gpperfmon_install createstwoentries:

localgpperfmongpmonmd5hostallgpmon127.0.0.1/28md5

IfyouauthenticateuserswithKerberos,youcanalsosetupKerberosauthenticationforthe gpmon roleontheGreenplummasterandstandbyhosts.KerberosauthenticationissupportedwithTCPconnectionsonly; local entriesuseLinuxsocketsandauthenticatewiththe .pgpass filepassword,evenifyouhaveenabledKerberosfor host entries.

ChangingthegpmonPasswordTochangethe gpmon password,followthesesteps:

1. LogintoGreenplumDatabaseasasuperuserandchangethe gpmon passwordwiththe ALTERROLE command:

#ALTERROLEgpmonWITHENCRYPTEDPASSWORD'new_password';

2. Updatethepasswordinthe .pgpass fileinthe gpadmin homedirectory( ~/.pgpass ).Replacetheexistingpasswordinthelineorlinesfor gpmon withthenewpassword.

*:5432:gpperfmon:gpmon:new_password

3. Ensurethatthe .pgpass fileisownedby gpadmin andRW-accessibleby gpadmin only.

$chowngpadmin:gpadmin~/.pgpass$chmod600~/.pgpass

4. RestartGreenplumCommandCenterwiththe gpcmdr utility.

$gpcmdr--restart

AuthenticatinggpmonwithKerberosIfyouauthenticateGreenplumDatabaseandCommandCenteruserswithKerberos,youcanalsoauthenticatethe gpmon userwithKerberos.

1. OntheKDC,createakeytabfilecontainingtheKerberosprincipalforthe gpmon user,justasyouwouldforanyKerberos-authenticatedclient.InstallthefileontheGreenplummasterandstandbyhosts.

2. Updatetheentriesfor gpmon inthe $MASTER_DATA_DIRECTORY/pg_hba.conf filetousethe gss authenticationmethod.

hostallgpmon0.0.0.0/0gssinclude_realm=0krb_realm=GPDB.EXAMPLE.COM

Notethat local entriesin pg_hba.conf cannotbeauthenticatedwithKerberos.Ifthereisa local entryforthe gpmon user,itwillusethe .pgpass fileto

©CopyrightPivotalSoftwareInc,2013-2016 58 3.1.1

Page 59: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

authenticatewiththedatabase.SeeThepg_hba.conffile inthePostgreSQLdocumentationforcomplete pg_hba.conf filedocumentation.

1. Logintothemasterhostas gpadmin andauthenticatethe gpmon user.

$kinitgpmon

1. CreatetheKerberos-enabledCommandCenterConsoleinstance.SeeCreatingGreenplumCommandCenterConsoleInstancesforstepstocreateaninstance.

©CopyrightPivotalSoftwareInc,2013-2016 59 3.1.1

Page 60: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

UtilityReferenceReferenceinformationforthetwoGreenplumCommandCenterutilityprograms:the gpperfmon_install utilitythatenablesthedatacollectionagentsandthe gpcmdr utilitythatsetsupandmanagesthewebapplication.

gpperfmon_install

gpcmdr

©CopyrightPivotalSoftwareInc,2013-2016 60 3.1.1

Page 61: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

gpperfmon_installInstallstheCommandCenterdatabase(gpperfmon)andoptionallyenablesthedatacollectionagents.

gpperfmon_install[--enable--passwordgpmon_password--portgpdb_port][--pgpasspath_to_file][–verbose]

gpperfmon_install--help|-h|-?

–enable

Inadditiontocreatingthe gpperfmon database,performstheadditionalstepsrequiredtoenabletheCommandCenterdatacollectionagents.When --enable isspecifiedtheutilitywillalsocreateandconfigurethegpmonsuperuseraccountandsettheCommandCenterserverconfigurationparametersinthe postgresql.conf files.

–passwordgpmon_passwordRequiredif --enable isspecified.Setsthepasswordofthegpmonsuperuser

–portgpdb_portRequiredif --enable isspecified.SpecifiestheconnectionportoftheGreenplumDatabasemaster.

–pgpasspath_to_fileOptionalif --enable isspecified.Ifthepasswordfileisnotinthedefaultlocationof ~/.pgpass ,specifiesthelocationofthepasswordfile.

–verbose Setstheloggingleveltoverbose.

–help|-h|-? Displaystheonlinehelp.

DescriptionThe gpperfmon_install utilityautomatesthestepstoenabletheCommandCenterdatacollectionagents.YoumustbetheGreenplumsystemuser( gpadmin

)torunthisutility.Ifusingthe --enable option,theGreenplumDatabaseinstancemustberestartedaftertheutilitycompletes.

Whenrunwithoutanyoptions,theutilitywilljustcreatetheCommandCenterdatabase(gpperfmon).Whenrunwiththe–enableoption,theutilitywillalsorunthefollowingadditionaltasksnecessarytoenabletheCommandCenterdatacollectionagents:

1. Createsthe gpmon superuserroleinGreenplumDatabase.TheCommandCenterdatacollectionagentsrequirethisroletoconnecttothedatabaseandwritetheirdata.The gpmon superuserroleusesMD5-encryptedpasswordauthenticationbydefault.Usethe–passwordoptiontosetthegpmon superuser’spassword.Usethe --port optiontosupplytheportoftheGreenplumDatabasemasterinstance.

2. Updatesthe $MASTER_DATA_DIRECTORY/pg_hba.conf file.Theutilityaddsthefollowinglinestothehost-basedauthenticationfile( pg_hba.conf ).Thisallowsthe gpmon usertolocallyconnecttoanydatabaseusingMD5-encryptedpasswordauthentication:

localgpperfmongpmonmd5hostallgpmon127.0.0.1/28md5

3. Updatesthepasswordfile( .pgpass ).Inordertoallowthedatacollectionagentstoconnectasthe gpmon rolewithoutapasswordprompt,youmusthaveapasswordfilethathasanentryforthe gpmon user.Theutilityaddsthefollowingentrytoyourpasswordfile(ifthefiledoesnotexist,theutilitycreatesit):

*:5432:gpperfmon:gpmon:gpmon_password

Ifyourpasswordfileisnotlocatedinthedefaultlocation( ~/.pgpass ),usethe --pgpass optiontospecifythefilelocation.

4. SetstheserverconfigurationparametersforCommandCenter.Thefollowingparametersmustbeenabledinorderforthedatacollectionagentstobegincollectingdata.Theutilitywillsetthefollowingparametersinthe postgresql.conf configurationfiles:

gp_enable_gpperfmon=on (inall postgresql.conf files)gpperfmon_port=8888 (inall postgresql.conf files)gp_external_enable_exec=on (inthemaster postgresql.conf file)

©CopyrightPivotalSoftwareInc,2013-2016 61 3.1.1

Page 62: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ExamplesCreatetheCommandCenterdatabase( gpperfmon )only:

$su-gpadmin$gpperfmon_install

CreatetheCommandCenterdatabase( gpperfmon ),createthe gpmon superuser,andenabletheCommandCenteragents:

$su-gpadmin$gpperfmon_install--enable--passwordchangeme--port5432$gpstop-r

©CopyrightPivotalSoftwareInc,2013-2016 62 3.1.1

Page 63: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

gpcmdrConfiguresandmanagesinstancesoftheCommandCenterConsole.

gpcmdr[--ssh_full_path<path>]--setup[[<section_header>]--config_file<path>]|--start[<instance_name>]|--stop[<instance_name>]|--restart[<instance_name>]|--migrate[<instance_name>]|--remove[<instance_name>]|--status[<instance_name>]

Type Description

--setup

Configuresconsolecomponentsontheinstallationhost.Withthisoption, gpcmdr promptsforvaluestoconfigurethecomponentsandwritesthevaluesto app.conf .Formoreinformationontheseconfigurationparameters,seeConfigurationFileReference.

--config_file

SetsthepathtoaconfigurationfiletousetosetupnewCommandCenterinstances.Thisoptionmustbeusedwiththe --setupoption.SeeSetupConfigurationFileforinformationabouttheformatandcontentofthisconfigurationfile.Ifsection_headerissupplied, gpcmdr onlysetsuptheinstancedefinedinthenamedsectionintheconfigurationfile.Otherwise, gpcmdr setsupallinstancesintheconfigurationfile.

--start Startsthespecifiedinstance(orallinstancesbydefault)anditsassociatedwebservice.

--stop Stopsthespecifiedinstance(orallinstancesbydefault)anditsassociatedwebservice.

--migrate CopiesCommandCenterinstances(orallinstancesbydefault)fromapreviousinstallation.

--remove Removesthespecifiedinstanceanditsassociateddatabaseschema.

--restart Restartsthespecifiedinstance(orallinstancesbydefault)anditsassociatedwebservice.

--status Displaysthestatus,either Running or Stopped ,ofthewebservice.

--version Displaystheversionofthe gpcmdr utility.

--ssh_full_path

Setsthefullpathtothesshcommand.Usethistooverridethesshcommandfoundonthepath.

DescriptionThe gpcmdr utilitysetsupandconfiguresCommandCenterConsoleinstances,startsandstopsinstances,andprovidesstatusinformation.

YoucansetupanewCommandCenterConsoleinstanceinteractivelyor,byprovidingaconfigurationfile,non-interactively.

Foractions --start , --stop , --restart , --migrate ,and --status youcanspecifyaconsoleinstancename.Ifyoudonotspecifyaname,theactionappliestoallexistingconsoleinstances.

Onthe --start option, gpcmdr createsthe gpcc_basic , gpcc_operator_basic ,and gpcc_operator databaserolesiftheydonotalreadyexist.

The --migrate optionpromptsyoutoenterthepathtotheCommandCenterinstallationwithinstancesyouwanttomigrate.Theutilitycheckswhethertheinstancetocopyalreadyexistsinthenewlocationbeforecopying.Iftheinstanceexistsinthenewlocation,apromptaskswhetheryouwanttooverwritetheinstance.

ExamplesInteractivelycreateanewCommandCenterConsoleinstance:

$gpcmdr--setup

SetuptheCommandCenterConsoleinstancedefinedinthe [development] sectionofaconfigurationfile:

$gpmcdr--setupdevelopmentgpccinstances.cfg

CheckthestatusofallCommandCenterConsoleinstances:

©CopyrightPivotalSoftwareInc,2013-2016 63 3.1.1

Page 64: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

$gpcmdr--status

©CopyrightPivotalSoftwareInc,2013-2016 64 3.1.1

Page 65: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ConfigurationFileReferenceReferencesforGreenplumCommandCenterconfigurationfiles.

ConfigurationparametersforGreenplumCommandCenterarestoredinthefollowingfiles:

$MASTER_DATA_DIRECTORY/gpperfmon/conf/gpperfmon.conf

StoresconfigurationparametersfortheGreenplumCommandCenteragents.$GPPERFMONHOME/instances/<instance_name>/webserver/conf/app.conf

StoresconfigurationparametersfortheCommandCenterwebapplicationandwebserver.$MASTER_DATA_DIRECTORY/postgresql.conf

StoresconfigurationparameterstoenabletheGreenplumCommandCenterfeatureforGreenplumDatabaseserver.$GPPERFMONHOME/bin/ssh-wrapper

GreenplumCommandCenternormallyfindsthe ssh commandonthepath.Ifyourenvironmenthasanincompatibleimplementationofthiscommandonthepath,youcanprovidetheabsolutepathtoyourversioninthe ssh-wrapper script,locatedat$GPPERFMONHOME/bin/ssh-wrapper .

Forexample:

ssh="/home/me/bin/myssh"

Anysystemuserwithwritepermissionstothesedirectoriescanedittheseconfigurationfiles.

©CopyrightPivotalSoftwareInc,2013-2016 65 3.1.1

Page 66: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CommandCenterAgentParametersThe $MASTER_DATA_DIRECTORY/gpperfmon/conf/gpperfmon.conf filestoresconfigurationparametersfortheCommandCenteragents.Forconfigurationchangestotheseoptionstotakeeffect,youmustsave gpperfmon.conf andthenrestartGreenplumDatabaseserver( gpstop-

r).

ToenabletheCommandCenteragentswithinGreenplumDatabaseserver,youmustalsosettheGreenplumDatabaseServerConfigurationParameters,seeCommandCenterDatabaseReferencefordetails.

log_locationSpecifiesadirectorylocationforCommandCenterlogfiles.Defaultis $MASTER_DATA_DIRECTORY/gpperfmon/logs .

min_query_timeSpecifiestheminimumqueryruntimeinsecondsforstatisticscollection.CommandCenterlogsallqueriesthatrunlongerthanthisvalueinthequeries_historytable.Forquerieswithshorterruntimes,nohistoricaldataiscollected.Defaultsto20seconds.

Ifyouknowthatyouwanttocollectdataforallqueries,youcansetthisparametertoalowvalue.Settingtheminimumqueryruntimetozero,however,collectsdataevenforthenumerousqueriesrunbyCommandCenteritself,creatingalargeamountofdatathatmaynotbeuseful.

min_detailed_query_timeSpecifiestheminimumiteratorruntimeinsecondsforstatisticscollection.CommandCenterlogsalliteratorsthatrunlongerthanthisvalueintheiterators_historytable.Foriteratorswithshorterruntimes,nodataiscollected.Minimumvalueis10seconds.

Thisparameter’svaluemustalwaysbeequalto,orgreaterthan,thevalueof min_query_time .Setting min_detailed_query_time higherthanmin_query_time allowsyoutologdetailedqueryplaniteratordataonlyforespeciallycomplex,long-runningqueries,whilestillloggingbasicquerydataforshorterqueries.

Giventhecomplexityandsizeofiteratordata,youmaywanttoadjustthisparameteraccordingtothesizeofdatacollected.Ifthe iterators_* tablesaregrowingtoexcessivesizewithoutprovidingusefulinformation,youcanraisethevalueofthisparametertologiteratordetailforfewerqueries.

max_log_sizeThisparameterisnotincludedingpperfmon.conf,butitmaybeaddedtothisfileforusewithGreenplumCommandCenter.

Topreventthelogfilesfromgrowingtoexcessivesize,youcanaddthe max_log_size parameterto gpperfmon.conf .Thevalueofthisparameterismeasuredinbytes.Forexample:

max_log_size=10485760

Withthissetting,thelogfileswillgrowto10MBbeforethesystemrollsovertoanewlogfile.

partition_ageThenumberofmonthsthatGreenplumCommandCenterstatisticsdatawillberetained.Thedefaultitis0,whichmeanswewon’tdropanydata.

quantumSpecifiesthetimeinsecondsbetweenupdatesfromCommandCenteragentsonallsegments.Validvaluesare10,15,20,30,and60.Defaultsto15seconds.

Ifyoupreferalessgranularviewofperformance,orwanttocollectandanalyzeminimalamountsofdataforsystemmetrics,chooseahigherquantum.Tocollectdatamorefrequently,choosealowervalue.

ignore_qexec_packetWhensettotrue,GreenplumCommandCenteragentsdonotcollectperformancedatainthe gpperfmon database queries_* tables:rows_out , cpu_elapsed , cpu_currpct , skew_cpu ,and skew_rows .Thedefaultsetting,true,reducestheamountofmemoryconsumedbythegpmmonprocess.Setthisparametertofalseifyourequirethisadditionalperformancedata.

smdw_aliasesThisparameterallowsyoutospecifyadditionalhostnamesforthestandbymaster.Forexample,ifthestandbymasterhastwoNICs,youcanenter:

smdw_aliases=smdw-1,smdw-2

ThisoptionalfaulttoleranceparameterisusefuliftheGreenplumCommandCenterlosesconnectivitywiththestandbymaster.Insteadofcontinuouslyretryingtoconnecttohostsmdw,itwilltrytoconnecttotheNIC-basedaliasesof smdw-1 and/or smdw-2 .ThisensuresthattheCommandCenterConsolecancontinuouslypollandmonitorthestandbymaster.

©CopyrightPivotalSoftwareInc,2013-2016 66 3.1.1

Page 67: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

©CopyrightPivotalSoftwareInc,2013-2016 67 3.1.1

Page 68: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CommandCenterConsoleParametersEachinstanceoftheCommandCenterConsolehasaconfigurationfilelocatedat $GPPERFMONHOME/instances/<instance_name>/webserver/conf/app.conf .

Aftereditingthisfile,reloadtheconfigurationbyrestartingtheCommandCenterConsoleinstance( gpperfmon--restart<instance_name>

).

appname = gpmonws

Thewebserverbinaryfile.Donotchange.

listentcp4 = [true | false]

When true ,theaddresstypeistcp4.Thedefaultis true .

runmode = [prod | dev | test]

Theapplicationmode,whichcanbe dev , prod or test .Thedefaultis dev .In dev modeCommandCentershowsuserfriendlyerrorpages.Userfriendlyerrorpagesarenotrenderedin prod mode.

session = [true | false]

Usesessionstomanageuserexperience.Thedefaultis true .Sessionsarestoredinmemory.

enablexsrf = [true | false]

EnableCSRFprotection.

xsrfexpire = <seconds>

CSRFexpiretime.Thedefaultis 43200 seconds.

xsrfkey = <token_string>

TheCSRFtoken.

rendertype = json

Therendertypeofwebserver.Donotchange.

printallsqls = [true | false]

PrintallbackendgpperfmonSQLtothewebserverconsole.Thedefaultis false .

sessionname = webserver_gpperfmon_instance_<instance_name>

ThenameofthesessioninGreenplumDatabase.Donotchange.

display_name = <display_name>

Thedisplaynameforconsole.

master_host = <hostname>

TheGreenplumDatabasehostname.Thedefaultis localhost .

master_port = <port>

TheGreenplumDatabasemasterport.Thedefaultis 5432 .

HTTPSCertFile = </path/to/cert.pem>

Thefullpathtotheserver’sSSLcertificate,ifSSLisenabled.

HTTPSKeyFile = </path/to/cert.pem>

Theserver’sprivatekeyfileifSSLisenabled.

EnableHTTPS = [true | false]

EnablelisteningonthesecureSSLport.Thedefaultis true .

EnableHTTP = [true | false]

EnablelisteningontheHTTPport.Defaultis false .

httpsport = [port]

Thewebserverport.Thedefaultis28080.

©CopyrightPivotalSoftwareInc,2013-2016 68 3.1.1

Page 69: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

SetupConfigurationFileAsetupconfigurationfilecontainspropertiesusedtodefineoneormoreGreenplumCommandCenterinstanceswhen gpcmdr isrunwiththe--config_file option.

TheconfigurationfileusesthePythonconfigurationfileformat,similartotheMicrosoftINIfileformat.Thefilecontainssections,introducedbya[section] header,andfollowedby name:value or name=value entries,oneperline.Commentsbeginwitha # or ; characterandcontinuethroughtheendoftheline.A [DEFAULT] sectionsetsdefaultvaluesforparametersthatmaybeoverrideninothersections.

SeeSettingUpCommandCenterInstanceswithaConfigurationFile formoreinformation.

Parametersremote_db

True iftheinstanceistorunonadifferenthost.Default: False .

master_host

ThenameofthehostwheretheGreenplumCommandCenterConsoleistobesetup,if remote_db is True .

instance_name

Thenameoftheinstancetosetup.Thiswillbecomethenameofasubdirectoryinthe instances directorywheretheinstancesconfigurationandlogfilesarestored.Instancenamesmaycontainletters,digits,andunderscoresandarenotcasesensitive.

display_name

ThenametodisplayfortheinstanceintheCommandCenteruserinterface.Displaynamesmaycontainletters,digits,andunderscoresandarecasesensitive. instance_name isusedfor display_name ifthisparameterisnotprovided.

master_port

TheGreenplumDatabasemasterport.Default: 5432 .

webserver_port

ThelistenportfortheCommandCentergowebserver.ThisportmustbedifferentforeachCommandCenterConsoleinstanceonthehost.Default:28080 .

enable_ssl

True ifclientconnectionstotheCommandCenterwebservershouldbesecuredwithSSL.Default: False .

enable_user_cert

True iftheservercertificateissuppliedbytheuser.If False (default)and enable_ssl is True , gpcmdr generatesacertificateduringsetup.Dataforthecertificate’sCNisenteredinteractivelyduringsetup.Default: False .

ssl_cert_file

If enable_user_cert is True ,setthisparametertothefullpathtoavalidcertificateinPEMfileformat.

enable_kerberos

Setto True toenableKerberosauthentication.

webserver_url

Thewebserverhostname,fromtheKerberosHTTPserviceprincipal.

keytab

PathtothekeytabfilecontainingKerberosprincipalsfortheCommandCenterwebserverandusers.

enable_copy_standby

Setto True tohave gpcmdr installtheinstanceconfigurationontheGreenplumstandbymasterhost.

standby_master_host

ThenameoftheGreenplumstandbymasterhost.Requiredwhen enable_copy_standby is True .

Examples

©CopyrightPivotalSoftwareInc,2013-2016 69 3.1.1

Page 70: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ThisexampleconfigurationsetsuptwoCommandCenterinstances, prod and dev .Parametersinthe [DEFAULT] sectionapplytoallinstancesandmaybeoverriddenbyparametersinthe [production] and [development] sections.

[DEFAULT]remote_db=falsemaster_port=5432#Youneedtoset'enable_user_cert'totruetoimportyourownpemfileenable_user_cert=truessl_cert_file=/tmp/cert.pem

[development]instance_name=developmentenable_copy_standby=falsewebserver_port=28080enable_ssl=false

[production]instance_name=productiondisplay_name=OurProductionremote_db=truemaster_host=mdwmaster_port=15432webserver_port=28081enable_ssl=trueenable_user_cert=trueenable_copy_standby=truestandby_master_host=smdw

Thisexampleconfigurationhasonlyoneinstance,sothe [DEFAULT] sectionandsectionheadersarenotnecessary.

instance_name=singledisplay_name=SINGLEremote_db=truemaster_host=10.152.10.149master_port=5432webserver_port=28082enable_ssl=trueenable_user_cert=truessl_cert_file=/tmp/cert.pemenable_copy_standby=truestandby_master_host=192.0.2.156

©CopyrightPivotalSoftwareInc,2013-2016 70 3.1.1

Page 71: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

GreenplumDatabaseServerConfigurationParametersThefollowingparametersmustbeuncommentedandsetintheserverconfigurationfile( postgresql.conf )inordertoenabletheCommandCenterdatacollectionagents:

gp_enable_gpperfmon and gpperfmon_port mustbesetinboththemasterandsegment postgresql.conf files.

gp_enable_gpperfmon and gp_enable_gpperfmon onlyneedtobesetinthemaster postgresql.conf file.

Afterchangingthesesettings,theGreenplumDatabaseinstancemustberestartedforthechangestotakeeffect.

gp_enable_gpperfmonTurnsontheCommandCenterdatacollectionagentforasegment.Mustbesetinall postgresql.conf files(masterandallsegments).

gpperfmon_port

ThedefaultportfortheCommandCenteragentsis8888,butyoucansetthisparametertoadifferentportifrequired(masterandallsegments).

gp_gpperfmon_send_intervalSetsthefrequencyinsecondsthattheGreenplumDatabaseserverprocessessendqueryexecutionupdatestotheCommandCenteragentprocesses.

gp_external_enable_execThisparameterisenabledbydefaultandmustremainenabled.ItallowstheuseofexternaltablesthatexecuteOScommandsorscriptsonthesegmenthosts.TheCommandCenteragentsusethistypeofexternaltablestocollectcurrentsystemmetricsfromthesegments.

gpperfmon_log_alert_levelControlswhichmessagelevelsarewrittentothegpperfmonlog.Eachlevelincludesallthelevelsthatfollowit.Thelaterthelevel,thefewermessagesaresenttothelog.Thedefaultvalueiswarning.

©CopyrightPivotalSoftwareInc,2013-2016 71 3.1.1

Page 72: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CommandCenterDatabaseReferenceReferencesfortheGreenplumCommandCenter gpperfmon databasetables.

TheCommandCenterdatabaseconsistsofthreesetsoftables; now tablesstoredataoncurrentsystemmetricssuchasactivequeries, history tablesstoredataonhistoricalmetrics,and tail tablesarefordataintransition. Tail tablesareforinternaluseonlyandshouldnotbequeriedbyusers.Thenow and tail dataarestoredastextfilesonthemasterhostfilesystem,andaccessedbytheCommandCenterdatabaseviaexternaltables.Thehistory tablesareregulardatabasetablesstoredwithintheCommandCenter( gpperfmon )database.

Thedatabaseconsistsofthreesetsoftables:

now tablesstoredataoncurrentsystemmetricssuchasactivequeries.

history tablesstoredatahistoricalmetrics.

tail tablesarefordataintransition.Thesetablesareforinternaluseonlyandshouldnotbequeriedbyendusers.

Thedatabasecontainsthefollowingcategoriesoftables:

Thedatabase_*tablesstorequeryworkloadinformationforaGreenplumDatabaseinstance.

Theemcconnect_historytabledisplaysinformationaboutConnectEMCeventsandalerts.ConnectEMCeventsaretriggeredbasedonahardwarefailure,afixtoafailedhardwarecomponent,oraGreenplumDatabasestartup.OnceanConnectEMCeventistriggered,analertissenttoEMCSupport.

Thediskspace_*tablesstorediskspacemetrics.

Thefilerep_*tablesstorehealthandstatusmetricsforthefilereplicationprocess.Thisprocessishowhigh-availability/mirroringisachievedinGreenplumDatabaseinstance.Statisticsaremaintainedforeachprimary-mirrorpair.

Thehealth_*tablesstoresystemhealthmetricsfortheEMCDataComputingAppliance.

Theinterface_stats_*tablesstorestatisticalmetricsforeachactiveinterfaceofaGreenplumDatabaseinstance.Note:Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

Theiterators_*tablesstoreinformationaboutqueryplaniteratorsandtheirmetrics.Aqueryiteratorreferstoanodeoroperationinaqueryplan.

Thelog_alert_*tablesstoreinformationaboutpg_logerrorsandwarnings.

Thequeries_*tablesstorehigh-levelquerystatusinformation.

Thesegment_*tablesstorememoryallocationstatisticsfortheGreenplumDatabasesegmentinstances.

Thesocket_stats_*tablesstorestatisticalmetricsaboutsocketusageforaGreenplumDatabaseinstance.Note:Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

Thesystem_*tablesstoresystemutilizationmetrics.

Thetcp_stats_*tablesstorestatisticalmetricsaboutTCPcommunicationsforaGreenplumDatabaseinstance.Note:Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

Theudp_stats_*tablesstorestatisticalmetricsaboutUDPcommunicationsforaGreenplumDatabaseinstance.Note:Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

TheCommandCenterdatabasealsocontainsthefollowingviews:

Thedynamic_memory_infoviewshowsanaggregateofallthesegmentsperhostandtheamountofdynamicmemoryusedperhost.

Theiterators_*_rollupsetofviewssummarizethequeryiteratormetricsacrossallsegmentsinthesystem.

Thememory_infoviewshowsper-hostmemoryinformationfromthe system_history and segment_history tables.

©CopyrightPivotalSoftwareInc,2013-2016 72 3.1.1

Page 73: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

database_*The database_* tablesstorequeryworkloadinformationforaGreenplumDatabaseinstance.Therearethreedatabasetables,allhavingthesamecolumns:

database_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentqueryworkloaddataisstoredin database_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttothedatabase_history table.

database_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforqueryworkloaddatathathasbeenclearedfromdatabase_nowbuthasnotyetbeencommittedto database_history .Ittypicallyonlycontainsafewminutesworthofdata.

database_history isaregulartablethatstoreshistoricaldatabase-widequeryworkloaddata.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

ctime timestamp Timethisrowwascreated.

queries_total int ThetotalnumberofqueriesinGreenplumDatabaseatdatacollectiontime.

queries_running int Thenumberofactivequeriesrunningatdatacollectiontime.

queries_queued int Thenumberofquerieswaitinginaresourcequeueatdatacollectiontime.

©CopyrightPivotalSoftwareInc,2013-2016 73 3.1.1

Page 74: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

emcconnect_historyThe emcconnect_history tabledisplaysinformationaboutConnectEMCeventsandalerts.ConnectEMCeventsaretriggeredbasedonahardwarefailure,afixtoafailedhardwarecomponent,oraGreenplumDatabaseinstancestartup.OnceanConnectEMCeventistriggered,analertissenttoEMCSupport.

Thistableispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedinonemonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Note:ThistableonlyappliestoGreenplumDataComputingApplianceplatforms.

ctime timestamp(0)withouttimezone TimethisConnectEMCeventoccurred.

hostname varchar(64)ThehostnameassociatedwiththeConnectEMCevent.

symptom_code int

Ageneralsymptomcodeforthistypeofevent.Foralistofsymptomcodes,seetheEMCGreenplumDCAInstallationandConfigurationGuide.

detailed_symptom_code int Aspecificsymptomcodeforthistypeofevent.

description textAdescriptionofthistypeofevent,basedonthedetailed_symptom_code .

snmp_oid textTheSNMPobjectIDoftheelement/componentwheretheeventoccurred,whereapplicable.

severity text

TheseverityleveloftheConnectEMCevent.Oneof:

WARNING :Aconditionthatmightrequireimmediateattention.

ERROR :AnerroroccurredontheDCA.Systemoperationand/orperformanceislikelyaffected.Thisalertrequiresimmediateattention.

UNKNOWN :ThisseveritylevelisassociatedwithhostsanddevicesontheDCAthatareeitherdisabled(duetohardwarefailure)orunreachableforsomeotherreason.Thisalertrequiresimmediateattention.

INFO :Apreviouslyreportederrorconditionisnowresolved.GreenplumDatabasestartupalsotriggersanINFOalert.

status text

Thecurrentstatusofthesystem.Thestatusisalways OK unlessaconnectiontotheserver/switchcannotbemade,inwhichcasethestatusis FAILED .

attempted_transport boolean

True ifanattemptwasmadetosendanalerttoEMCsupport.

False ifyoursystemwasconfigurednottosendalerts.

message textThetextoftheerrormessagecreatedasaresultofthisevent.

©CopyrightPivotalSoftwareInc,2013-2016 74 3.1.1

Page 75: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

diskspace_*The diskspace_* tablesstorediskspacemetrics.

diskspace_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentdiskspacemetricsarestoredin database_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttothediskspace_history table.

diskspace_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltablefordiskspacemetricsthathavebeenclearedfrom diskspace_now buthasnotyetbeencommittedto diskspace_history .Ittypicallyonlycontainsafewminutesworthofdata.

diskspace_history isaregulartablethatstoreshistoricaldiskspacemetrics.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

ctime timestamp(0)withouttimezone Timeofdiskspacemeasurement.

hostname varchar(64) Thehostnameassociatedwiththediskspacemeasurement.

Filesystem text Nameofthefilesystemforthediskspacemeasurement.

total_bytes bigint Totalbytesinthefilesystem.

bytes_used bigint Totalbytesusedinthefilesystem.

bytes_available bigint Totalbytesavailableinfilesystem.

©CopyrightPivotalSoftwareInc,2013-2016 75 3.1.1

Page 76: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

filerep_*The filerep* tablesstorehigh-availabilityfilereplicationprocessinformationforaGreenplumDatabaseinstance.Therearethreefilereptables,allhavingthesamecolumns:

filerep_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentfilereplicationdataisstoredinfilerep_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttothe filerep_historytable.

filerep_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforfilereplicationdatathathasbeenclearedfrom filerep_now buthasnotyetbeencommittedto filerep_history .Ittypicallyonlycontainsafewminutesworthofdata.

filerep_history isaregulartablethatstoreshistoricaldatabase-widefilereplicationdata.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

ctime timestamp Timethisrowwascreated.

primary_measurement_microsec bigintThelengthoftimeoverwhichprimarymetrics(containedinUDPmessages)weregathered.

mirror_measurement_microsec bigintThelengthoftimeoverwhichmirrormetrics(containedinUDPmessages)weregathered.

primary_hostname varchar(64) Thenameoftheprimaryhost.

primary_port int Theportnumberoftheprimaryhost.

mirror_hostname varchar(64) Thenameofthemirrorhost.

mirror_port int Theportnumberofthemirrorhost.

primary_write_syscall_bytes_avg bigintTheaverageamountofdatawrittentodiskontheprimaryforwritesystemcallsperinterval.

primary_write_syscall_byte_max bigintThemaximumamountofdatawrittentodiskontheprimaryforwritesystemcallsperinterval.

primary_write_syscall_microsecs_avg bigintTheaveragetimerequiredforawritesystemcalltowritedatatodiskontheprimaryperinterval.

primary_write_syscall_microsecs_max bigint

Themaximumtimerequiredforawritesystem

calltowritedatatodiskontheprimaryperinterval.

primary_write_syscall_per_sec doubleprecisionThenumberofwritesystemcallsontheprimarypersecond.Itreflectsonlythetimetoqueuethewritetodiskinmemory.

primary_fsync_syscall_microsec_avg bigintTheaverageamountoftimerequiredforafilesyncsystemcalltowritedatatodiskontheprimaryperinterval.

primary_fsync_syscall_microsec_max bigintThemaximumamountoftimerequiredforafilesyncsystemcalltowritedatatodiskontheprimaryperinterval.

primary_fsync_syscall_per_sec doubleprecision

Thenumberoffilesyncsystemcallsontheprimarypersecond.Unlikewritesystemcallswhichreturnimmediatelyafterthedataisposted/queued,filesyncsystemcallswaitforalloutstandingwritestobewrittentodisk.Filesyncsystemcallvaluesinthiscolumnreflectactualdiskaccesstimesforpotentiallylargeamountsofdata.

primary_write_shmem_bytes_avg bigintTheaverageamountofdatawrittentoshared

©CopyrightPivotalSoftwareInc,2013-2016 76 3.1.1

Page 77: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

primary_write_shmem_bytes_avg bigintmemoryontheprimaryperinterval.

primary_write_shmem_bytes_max bigintThemaximumamountofdatawrittentosharedmemoryontheprimaryperinterval.

primary_write_shmem_microsec_avg bigintTheaverageamountoftimerequiredtowritedatatosharedmemoryontheprimaryperinterval.

primary_write_shmem_microsec_max bigintThemaximumamountoftimerequiredtowritedatatosharedmemoryontheprimaryperinterval.

primary_write_shmem_per_sec doubleprecisionThenumberofwritestosharedmemoryontheprimarypersecond.

primary_fsync_shmem_microsec_avg bigint

Theaverageamountoftimerequiredbythefilesyncsystemcalltowritedatatosharedmemoryontheprimaryperinterval.

primary_fsync_shmem_microsec_max bigintThemaximumamountoftimerequiredbythefilesyncsystemcalltowritedatatosharedmemoryontheprimaryperinterval.

primary_fsync_shmem_per_sec doubleprecision

Thenumberoffilesynccallstosharedmemoryontheprimarypersecond.Filesyncsystemcallvaluesinthiscolumnreflectactualdiskaccesstimesforpotentiallylargeamountsofdata.

primary_write_shmem_per_sec doubleprecisionThenumberofwritestosharedmemoryontheprimarypersecond.

primary_fsync_shmem_microsec_avg bigintTheaverageamountoftimerequiredbythefilesyncsystemcalltowritedatatosharedmemoryontheprimaryperinterval.

primary_fsync_shmem_microsec_max bigintThemaximumamountoftimerequiredbythefilesyncsystemcalltowritedatatosharedmemoryontheprimaryperinterval.

primary_fsync_shmem_per_sec doubleprecision

Thenumberoffilesynccallstosharedmemoryontheprimarypersecond.Filesyncsystemcallvaluesinthiscolumnreflectactualdiskaccesstimesforpotentiallylargeamountsofdata.

primary_roundtrip_fsync_msg_microsec_avg bigint

Theaverageamountoftimerequiredforaroundtripfilesyncbetweentheprimaryandthemirrorperinterval.Thisincludes:

1. Thequeuingofafilesyncmessagefromtheprimarytothemirror.

2. Themessagetraversingthenetwork.

3. Theexecutionofthefilesyncbythemirror.

4. Thefilesyncacknowledgementtraversingthenetworkbacktotheprimary.

Themaximumamountoftimerequiredforaroundtripfilesyncbetweentheprimaryandthemirrorperinterval.Thisincludes:

©CopyrightPivotalSoftwareInc,2013-2016 77 3.1.1

Page 78: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

primary_roundtrip_fsync_msg_microsec_max bigint

1. Thequeuingofafilesyncmessagefromtheprimarytothemirror.

2. Themessagetraversingthenetwork.

3. Theexecutionofthefilesyncbythemirror.

4. Thefilesyncacknowledgementtraversingthenetworkbacktotheprimary.

primary_roundtrip_fsync_msg_per_sec doubleprecision Thenumberofroundtripfilesyncspersecond.

primary_roundtrip_test_msg_microsec_avg bigint

Theaverageamountoftimerequiredforaroundtriptestmessagebetweentheprimaryandthemirrortocompleteperinterval.Thisissimilarto primary_roundtrip_fsync_msg_microsec_avg ,exceptitdoesnotincludeadiskaccesscomponent.Becauseofthis,thisisausefulmetricthatshowstheaverageamountofnetworkdelayinthefilereplicationprocess.

primary_roundtrip_test_msg_microsec_max bigint

Themaximumamountoftimerequiredforaroundtriptestmessagebetweentheprimaryandthemirrortocompleteperinterval.Thisissimilarto primary_roundtrip_fsync_msg_microsec_max

,exceptitdoesnotincludeadiskaccesscomponent.Becauseofthis,thisisausefulmetricthatshowsthemaximumamountofnetworkdelayinthefilereplicationprocess.

primary_roundtrip_test_msg_per_sec doubleprecision

Thenumberofroundtripfilesyncspersecond.Thisissimilartoprimary_roundtrip_fsync_msg_per_sec ,exceptitdoesnotincludeadiskaccesscomponent.Assuch,thisisausefulmetricthatshowstheamountofnetworkdelayinthefilereplicationprocess.

Notethattestmessagestypicallyoccuronceperminute,soitiscommontoseeavalueof“0”fortimeperiodsnotcontainingatestmessage.

mirror_write_syscall_size_avg bigintTheaverageamountofdatawrittentodiskonthemirrorforwritesystemcallsperinterval.

mirror_write_syscall_size_max bigintThemaximumamountofdatawrittentodiskonthemirrorforwritesystemcallsperinterval.

mirror_write_syscall_microsec_avg bigintTheaveragetimerequiredforawritesystemcalltowritedatatodiskonthemirrorperinterval.

mirror_write_syscall_microsec_max bigintThemaximumtimerequiredforawritesystemcalltowritedatatodiskonthemirrorperinterval.

primary_roundtrip_test_msg_per_sec doubleprecision

Thenumberofroundtripfilesyncspersecond.Thisissimilartoprimary_roundtrip_fsync_msg_per_sec ,exceptitdoesnotincludeadiskaccesscomponent.Assuch,thisisausefulmetricthatshowstheamountofnetworkdelayinthefilereplicationprocess.

©CopyrightPivotalSoftwareInc,2013-2016 78 3.1.1

Page 79: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

Notethattestmessagestypicallyoccuronceperminute,soitiscommontoseeavalueof“0”fortimeperiodsnotcontainingatestmessage.

mirror_write_syscall_size_avg bigintTheaverageamountofdatawrittentodiskonthemirrorforwritesystemcallsperinterval.

mirror_write_syscall_size_max bigint

Themaximumamountofdatawrittentodisk

onthemirrorforwritesystemcallsperinterval.

mirror_write_syscall_microsec_avg bigintTheaveragetimerequiredforawritesystemcalltowritedatatodiskonthemirrorperinterval.

©CopyrightPivotalSoftwareInc,2013-2016 79 3.1.1

Page 80: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

health_*The health_* tablesstoresystemhealthmetricsfortheEMCDataComputingAppliance.Therearethreehealthtables,allhavingthesamecolumns:

Note:ThistableonlyappliestoGreenplumDataComputingApplianceplatforms.

health_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentsystemhealthdataisstoredinsystem_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttothe system_history table.

health_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforsystemhealthdatathathasbeenclearedfrom system_now buthasnotyetbeencommittedto system_history .Ittypicallyonlycontainsafewminutesworthofdata.

health_history isaregulartablethatstoreshistoricalsystemhealthmetrics.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

ctimetimestamp(0)withouttimezone

Timethissnapshotofhealthinformationaboutthissystemwascreated.

hostname varchar(64) Segmentormasterhostnameassociatedwiththishealthinformation.

symptom_code int Thesymptomcoderelatedtothecurrenthealth/statusofanelementorcomponentofthesystem.

detailed_symptom_code intAmoregranularsymptomcoderelatedtothehealth/statusofaelementorcomponentofthesystem.

description text Adescriptionofthehealth/statusofthissymptomcode.

snmp_oid text TheSNMPobjectIDoftheelement/componentwheretheeventoccurred,whereapplicable.

status textThecurrentstatusofthesystem.Thestatusisalways OK unlessaconnectiontotheserver/switchcannotbemade,inwhichcasethestatusis FAILED .

message text Thetextoftheerrormessagecreatedasaresultofthisevent.

©CopyrightPivotalSoftwareInc,2013-2016 80 3.1.1

Page 81: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

interface_stats_*The interface_stats_* tablesstorestatisticalmetricsaboutcommunicationsovereachactiveinterfaceforaGreenplumDatabaseinstance.

Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

Therearethree interface_stats tables,allhavingthesamecolumns:

interface_stats_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .

interface_stats_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforstatisticalinterfacemetricsthathasbeenclearedfrom interface_stats_now buthasnotyetbeencommittedto interface_stats_history .Ittypicallyonlycontainsafewminutesworthofdata.

interface_stats_history isaregulartablethatstoresstatisticalinterfacemetrics.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedinonemonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

interface_name string Nameoftheinterface.Forexample:eth0,eth1,lo.

bytes_received bigint Amountofdatareceivedinbytes.

packets_received bigint Numberofpacketsreceived.

receive_errors bigint Numberoferrorsencounteredwhiledatawasbeingreceived.

receive_drops bigint Numberoftimespacketsweredroppedwhiledatawasbeingreceived.

receive_fifo_errors bigint NumberoftimesFIFO(firstinfirstout)errorswereencounteredwhiledatawasbeingreceived.

receive_frame_errors bigint Numberofframeerrorswhiledatawasbeingreceived.

receive_compressed_packets int Numberofpacketsreceivedincompressedformat.

receive_multicast_packets int Numberofmulticastpacketsreceived.

bytes_transmitted bigint Amountofdatatransmittedinbytes.

packets_transmitted bigint Amountofdatatransmittedinbytes.

packets_transmitted bigint Numberofpacketstransmitted.

transmit_errors bigint Numberoferrorsencounteredduringdatatransmission.

transmit_drops bigint Numberoftimespacketsweredroppedduringdatatransmission.

transmit_fifo_errors bigint Numberoftimesfifoerrorswereencounteredduringdatatransmission.

transmit_collision_errors bigint Numberoftimescollisionerrorswereencounteredduringdatatransmission.

transmit_carrier_errors bigint Numberoftimescarriererrorswereencounteredduringdatatransmission.

transmit_compressed_packets int Numberofpacketstransmittedincompressedformat.

©CopyrightPivotalSoftwareInc,2013-2016 81 3.1.1

Page 82: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

iterators_*The iterators_* tablesstoreinformationaboutqueryplaniteratorsandtheirmetrics.Aqueryiteratorreferstoanodeoroperationinaqueryplan.Forexample,asequentialscanoperationonatablemaybeonetypeofiteratorinaparticularqueryplan.

The tmid , ssid and ccnt columnsarethecompositekeythatuniquelyidentifiesaparticularquery.Thesecolumnscanbeusedtojoinwiththequeries_* datatables.

Therearethreeiteratortables,allhavingthesamecolumns:

iterators_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentqueryplaniteratordataisstoredin iterators_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttotheiterators_history table.

iterators_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforqueryplaniteratordatathathasbeenclearedfrom iterators_now buthasnotyetbeencommittedto iterators_history .Ittypicallyonlycontainsafewminutesworthofdata.

iterators_history isaregulartablethatstoreshistoricalqueryplaniteratordata.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Seealsotheiterator_rollupviewsforsummarymetricsofthequeryplaniteratordata.

ctime timestamp Timethisrowwascreated.

tmid intAtimeidentifierforaparticularquery.Alliteratorrecordsassociatedwiththequerywillhavethesametmid.

ssid intThesessionidasshownbythe gp_session_idparameter.Alliteratorrecordsassociatedwiththequerywillhavethesame ssid .

ccnt int

Thecommandnumberwithinthissessionasshownby gp_command_count parameter.Alliteratorrecordsassociatedwiththequerywillhavethesame ccnt .

segid intThesegmentID( dbid fromgp_segment_configuration ).

pid int ThepostgresprocessIDforthisiterator.

nid int

ThequeryplannodeIDfromtheGreenplum

sliceplan.

pnid intTheparentqueryplannodeIDfromtheGreenplumsliceplan.

hostname varchar(64) Segmenthostname.

ntype varchar(64)Theiteratoroperationtype.Possiblevaluesarelistedin[IteratorMetrics](db-iterator-metrics.html).

nstatus varchar(64)Thestatusofthisiterator.Possiblevaluesare:Initialize,ExecutingandFinished.

tstart timestamp Starttimefortheiterator.

tduration int Durationoftheexecution.

pmemsize bigintMaximumworkmemoryallocatedbytheGreenplumplannertothisiterator’squeryprocess.

memsize bigint OSmemoryallocatedtothisiterator’sprocess.

memresid bigintResidentmemoryallocatedtothisiterator’sprocess(asopposedtosharedmemory).

Sharedmemoryallocatedtothisiterator’s

©CopyrightPivotalSoftwareInc,2013-2016 82 3.1.1

Page 83: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

memshare bigintSharedmemoryallocatedtothisiterator’sprocess.

cpu_elapsed bigintTotalCPUusageoftheprocessexecutingtheiterator.

cpu_currpct floatThepercentageofCPUcurrentlybeingutilizedbythisiteratorprocess.Thisvalueisalwayszeroforhistorical(completed)iterators.

rowsout bigintTheactualnumberofrowsoutputbytheiterator.

rowsout_est bigintThequeryplanner’sestimateofrowsoutputbytheiterator.

m0_name varchar(64)

Eachoperationinaqueryplan(ntype)has

metricsassociatedwithit.Foralloperations,thismetricnameis Rows In .

m0_unit varchar(64)Theunitofmeasureforthismetric.Foralloperations( ntype ),thisunitofmeasureisRows .

m0_val bigint Thevalueofthismetric.

m0_est bigint Theestimatedvalueofthismetric.

m1_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m1_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m1_val bigint Thevalueofthismetric.

m1_est bigint Theestimatedvalueofthismetric.

m2_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m2_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m2_val bigint Thevalueofthismetric.

m2_est bigint Theestimatedvalueofthismetric.

m3_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m3_unitvarchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)fora

completelistofiteratorattributesandtheircorrespondingunits.

m3_val bigint Thevalueofthismetric.

m3_est bigint Theestimatedvalueofthismetric.

m4_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorresponding

©CopyrightPivotalSoftwareInc,2013-2016 83 3.1.1

Page 84: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

iteratorattributesandtheircorrespondingunits.

m4_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m4_val bigint Thevalueofthismetric.

m4_est bigint Theestimatedvalueofthismetric.

m5_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m5_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m5_val bigint Thevalueofthismetric.

m5_est bigint Theestimatedvalueofthismetric.

m6_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m6_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m6_val bigint Thevalueofthismetric.

m6_est bigint Theestimatedvalueofthismetric.

m7_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m7_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m7_val bigint Thevalueofthismetric.

m7_est bigint Theestimatedvalueofthismetric.

m8_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m8_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m8_val bigint Theactualvalueofthismetric.

m8_est bigint Theestimatedvalueofthismetric.

m9_name varchar(64)

Eachoperationinaqueryplan( ntype )hasmetricsassociatedwithit.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

Theunitofmeasureforthismetric.See[Iterator

©CopyrightPivotalSoftwareInc,2013-2016 84 3.1.1

Page 85: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

m9_unit varchar(64)

Theunitofmeasureforthismetric.See[IteratorMetrics](db-iterator-metrics.html)foracompletelistofiteratorattributesandtheircorrespondingunits.

m9_val bigint Theactualvalueofthismetric.

m9_est bigint Theestimatedvalueofthismetric.

m10_name - m15_name varchar(64) Theiteratorname( ntype )associatedwiththismetric.Metrics m10 through m15 arecurrentlynotused.

m10_unit - m15_unit varchar(64)Theunitofmeasureforthismetric.Metricsm10 through m15 arecurrentlynotused.

m10_value - m15_value bigintTheactualvalueofthismetric.Metrics m10through m15 arecurrentlynotused.

m10_est - m15_est bigintTheestimatedvalueofthismetric.Metrics m10through m15 arecurrentlynotused.

t0_name varchar(64)Thiscolumnisalabelfor t0_val .Itsvalueisalways Name .

t0_val varchar(128)

Thenameoftherelationbeingscannedbyaniterator.Thismetriciscollectedonlyforiteratorsthatperformscanoperationssuchasasequentialscanorfunctionscan.

©CopyrightPivotalSoftwareInc,2013-2016 85 3.1.1

Page 86: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

IteratorMetricsThetablesinthissectionlistallpossibleiteratorsinaqueryonGreenplumDatabaseinstance.Theiteratortablesincludethemetricname,thecolumninthe iterators_* tableinthe gpperfmon databasewherethemetricappears,howthemetricismeasured(unit),andadescriptionofthemetric.

MetricTerminology

ThefollowinginformationexplainssomeofthedatabasetermsandconceptsthatappeariniteratormetricsinGreenplumDatabase:

NodeReferstoastepinaqueryplan.AqueryplanhassetsofoperationsthatGreenplumDatabaseperformstoproducetheanswertoagivenquery.Anodeintheplanrepresentsaspecificdatabaseoperation,suchasatablescan,join,aggregation,sort,etc.

IteratorRepresentstheactualexecutionofthenodeinaqueryplan.Nodeanditeratoraresometimesusedinterchangeably.

TupleReferstoarowreturnedaspartofaresultsetfromaquery,aswellasarecordinatable.

SpillWhenthereisnotenoughmemorytoperformadatabaseoperation,datamustbewritten(orspilled)todisk.

PassesOccurwhenaniteratormustscan(orpass)overspilleddatatoobtainaresult.Apassrepresentsonepassthroughallinputtuples,oralldatainbatchfilesgeneratedafterspill,whichhappenshierarchically.Inthefirstpass,allinputtuplesareread,andintermediateresultsarespilledtoaspecifiednumberofbatchfiles.Inthesecondpass,thedatainallbatchfilesisprocessed.Iftheresultsarestilltoolargetostoreinmemory,theintermediateresultsarespilledtothesecondlevelofspillfiles,andtheprocessrepeatsagain.

BatchesReferstotheactualfilescreatedwhendataisspilledtodisk.ThisismostoftenassociatedtoHashoperations.

JoinThisclauseinaqueryjoinstwoormoretables.TherearethreetypesofJoinalgorithmsinGreenplumDatabaseinstance:

HashJoin

MergeJoin

NestedLoop

EachoftheseoperationsincludetheirownrespectiveJoinsemantics.TheCommandCenterConsoledisplaysiteratormetricsforeachofthesesemantics.

Append

AnAppenditeratorhastwoormoreinputsets.Appendreturnsallrowsfromthefirstinputset,thenallrowsfromthesecondinputset,andsoon,untilallrowsfromallinputsetsareprocessed.Appendisalsousedwhenyouselectfromatableinvolvedinaninheritancehierarchy.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

AppendCurrentInputSource m1_name Inputs Thenumberofthecurrenttablebeingscanned.

Append-OnlyScan

Thisiteratorscansappend-onlytype-tables.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

Append-onlyScanRescan m1_name RescansThenumberofappend-onlyrescansbythisiterator.

Append-onlyColumnarScan

Thisiteratorscansappend-onlycolumnar-typetables.

Rowsin m0_name RowsThenumberoftuplesreceivedby

©CopyrightPivotalSoftwareInc,2013-2016 86 3.1.1

Page 87: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

theiterator.

Append-OnlyColumnarScanRescan

m1_name RescansThenumberofappend-onlycolumnarrescansbythisiterator.

Aggregate

Thequeryplannerproducesanaggregateiteratorwheneverthequeryincludesanaggregatefunction.Forexample,thefollowingfunctionsareaggregatefunctions: AVG() , COUNT() , MAX() , MIN() , STDDEV() , SUM() ,and VARIANCE() .Aggregatereadsalltherowsintheinputsetandcomputestheaggregatevalues.Iftheinputsetisnotgrouped,Aggregateproducesasingleresultrow.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

AggregateTotalSpillTuple m1_nameTuples

Thenumberoftuplesspilledtodisk

AggregateTotalSpillBytes m2_name Bytes Thenumberofbytesspilledtodisk.

AggregateTotalSpillBatches m3_name BatchesThenumberofspillbatchesrequired.

AggregateTotalSpillPass m4_name PassesThenumberofpassesacrossallofthebatches.

AggregateCurrentSpillPassReadTuples

m5_name TuplesThenumberofbytesreadinforthisspillbatch.

AggregateCurrentSpillPassReadBytes

m6_name BytesThenumberoftuplesreadinforthisspillbatch.

AggregateCurrentSpillPassTuples m7_name TuplesThenumberoftuplesthatareineachspillfileinthecurrentpass.

AggregateCurrentSpillPassBytes m8_name BytesThenumberofbytesthatareineachspillfileinthecurrentpass.

AggregateCurrentSpillPassBatches

m9_name BatchesThenumberofbatchescreatedinthecurrentpass.

BitmapAnd

ThisiteratortakesthebitmapsgeneratedfrommultipleBitmapIndexScaniterators,putsthemtogetherwithan AND clause,andgeneratesanewbitmapasitsoutput.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

BitmapOr

ThisiteratortakesthebitmapsgeneratedfrommultipleBitmapIndexScaniterators,putsthemtogetherwithan OR clause,andgeneratesanewbitmapasitsoutput.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

BitmapAppend-OnlyScan

ThisiteratorretrievesallrowsfromthebitmapgeneratedbyBitmapAnd,BitmapOr,orBitmapIndexScanandaccessestheappend-onlytabletoretrievetherelevantrows.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

BitmapHeapScan

ThisiteratorretrievesallrowsfromthebitmapgeneratedbyBitmapAnd,BitmapOr,orBitmapIndexScanandaccessestheheaptabletoretrievetherelevantrows.

©CopyrightPivotalSoftwareInc,2013-2016 87 3.1.1

Page 88: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

BitmapHeapScanPages m1_name Pages Thenumberofbitmapheappagesscanned.

BitmapHeapScanRescan m2_name Rescans Thenumberofbitmapheappagerescansbythisiterator.

BitmapIndexScan

Thisiteratorproducesabitmapthatcorrespondstotherulesthatsatisfythequeryplan.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

BitmapIndexScanRescan m1_name Rescans Thenumberofbitmapindexrescansbythisiterator.

BroadcastMotion

Notethatthe Motion metricsfortheiteratorareusefulwheninvestigatingpotentialnetworkingissuesintheGreenplumDatabasesystem.Typically,the“AckTime”valuesshouldbeverysmall(microsecondsormilliseconds).Howeverifthe“AckTime”valuesareoneormoreseconds(particularlythe“MotionMinAckTime”metric),thenanetworkperformanceissuelikelyexists.

Also,iftherearealargenumberofpacketsbeingdroppedbecauseofqueueoverflow,youcanincreasethevalueforthe gp_interconnect_queue_depth systemconfigurationparametertoimproveperformance.SeetheGreenplumDatabaseReferenceGuideformoreinformationaboutsystemconfigurationparameters.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

MotionBytesSent m1_name BytesThenumberofbytessentbytheiterator.

MotionTotalAckTime m2_name Microseconds

Thetotalamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionAverageAckTime m3_name Microseconds

Theaverageamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMaxAckTime m4_name Microseconds

Themaximumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMinAckTime m5_name Microseconds

Theminimumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionCountResent m6_name Packets

Thetotalnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.

MotionMaxResent m7_name Packets

Themaximumnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.Thismetricisappliedonaperpacketbasis.Forexample,avalueof“10”indicatesthataparticularpacketdidnotgetacknowledgedbythisiterator10times,andthatthiswasthemaximumforthisiterator.

MotionBytesReceived m8_name BytesThenumberofbytesreceivedbytheiterator.

©CopyrightPivotalSoftwareInc,2013-2016 88 3.1.1

Page 89: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

MotionCountDropped m9_name PacketsThenumberofpacketsdroppedbytheiteratorbecauseofbufferoverruns.

ExplicitRedistributeMotion

TheExplicitRedistributeiteratormovestuplestosegmentsexplicitlyspecifiedinthesegmentIDcolumnofthetuples.ThisdiffersfromaRedistributeMotioniterator,wheretargetsegmentsareindirectlyspecifiedthroughhashexpressions.TheExplicitRedistributeiteratorisusedwhenthequeryportionofaDMLplannedstatementrequiresmovingtuplesacrossdistributedtables.

NotethattheMotionmetricsfortheiteratorareusefulwheninvestigatingpotentialnetworkingissuesintheGreenplumDatabasesystem.Typically,the“AckTime”valuesshouldbeverysmall(microsecondsormilliseconds).Howeverifthe“AckTime”valuesareoneormoreseconds(particularlythe“MotionMinAckTime”metric),thenanetworkperformanceissuelikelyexists.

Also,iftherearealargenumberofpacketsbeingdroppedbecauseofqueueoverflow,youcanincreasethevalueforthe gp_interconnect_queue_depthsystemconfigurationparametertoimproveperformance.SeetheGreenplumDatabaseReferenceGuideformoreinformationaboutsystemconfigurationparameters.

.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

MotionBytesSent m1_name BytesThenumberofbytessentbytheiterator.

MotionTotalAckTime m2_name Microseconds

Thetotalamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionAverageAckTime m3_name Microseconds

Theaverageamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMaxAckTime m4_name Microseconds

Themaximumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMinAckTime m5_name Microseconds

Theminimumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionCountResent m6_name Packets

Thetotalnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.

MotionMaxResent m7_name Packets

Themaximumnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.Thismetricisappliedonaperpacketbasis.Forexample,avalueof“10”indicatesthataparticularpacketdidnotgetacknowledgedbythisiterator10times,andthatthiswasthemaximumforthisiterator.

MotionBytesReceived m8_name BytesThenumberofbytesreceivedbytheiterator.

MotionCountDropped m9_name PacketsThenumberofpacketsdroppedbytheiteratorbecauseofbufferoverruns.

©CopyrightPivotalSoftwareInc,2013-2016 89 3.1.1

Page 90: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

ExternalScan

Thisiteratorscansanexternaltable.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

ExternalScanRescan m1_name Rescans Thenumberofexternaltablerescansbythisiterator.

FunctionScan

Thisiteratorreturnstuplesproducedbyafunction.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

GatherMotion

Thisiteratorgathersstreamsoftuplesthataresentby“sending”motions.Ifamergekeyisspecified,itmergesmanystreamsintoasingleorder-preservedstream.

NotethattheMotionmetricsfortheiteratorareusefulwheninvestigatingpotentialnetworkingissuesintheGreenplumDatabasesystem.Typically,the“AckTime”valuesshouldbeverysmall(microsecondsormilliseconds).Howeverifthe“AckTime”valuesareoneormoreseconds(particularlythe“MotionMinAckTime”metric),thenanetworkperformanceissuelikelyexists.

Also,iftherearealargenumberofpacketsbeingdroppedbecauseofqueueoverflow,youcanincreasethevalueforthe gp_interconnect_queue_depthsystemconfigurationparametertoimproveperformance.SeetheGreenplumDatabaseReferenceGuideformoreinformationaboutsystemconfigurationparameters.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

MotionBytesSent m1_name BytesThenumberofbytessentbytheiterator.

MotionTotalAckTime m2_name Microseconds

Thetotalamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionAverageAckTime m3_name Microseconds

Theaverageamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMaxAckTime m4_name Microseconds

Themaximumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMinAckTime m5_name Microseconds

Theminimumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionCountResent m6_name Packets

Thetotalnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.

MotionMaxResent m7_name Packets

Themaximumnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.Thismetricisappliedonaperpacketbasis.Forexample,avalueof“10”indicatesthataparticularpacketdidnotgetacknowledgedbythisiterator10times,andthatthiswasthemaximumforthisiterator.

©CopyrightPivotalSoftwareInc,2013-2016 90 3.1.1

Page 91: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

MotionBytesReceived m8_name Bytes Thenumberofbytesreceivedbytheiterator.

MotionCountDropped m9_name PacketsThenumberofpacketsdroppedbytheiteratorbecauseofbufferoverruns.

GroupAggregate

TheGroupAggregateiteratorisawaytocomputevectoraggregates,anditisusedtosatisfya GROUPBY clause.AsingleinputsetisrequiredbytheGroupAggregateiterator,anditmustbeorderedbythegroupingcolumn(s).Thisiteratorreturnsasinglerowforauniquevalueofgroupingcolumns.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

AggregateTotalSpillTuples m1_name TuplesThenumberoftuplesspilledtodisk.

AggregateTotalSpillBytes m2_name Bytes Thenumberofbytesspilledtodisk.

AggregateTotalSpillBatches m3_name BatchesThenumberofspillbatchesrequired.

AggregateTotalSpillPass m4_name PassesThenumberofpassesacrossallofthebatches.

AggregateCurrentSpillPassReadTuples

m5_name TuplesThenumberofbytesreadinforthisspillbatch

AggregateCurrentSpillPassReadBytes

m6_name BytesThenumberoftuplesreadinforthisspillbatch

AggregateCurrentSpillPassTuples m7_name TuplesThenumberoftuplesthatareineachspillfileinthecurrentpass.

AggregateCurrentSpillPassBytes m8_name BytesThenumberofbytesthatareineachspillfileinthecurrentpass.

AggregateCurrentSpillPassBatches

m9_name BatchesThenumberofbatchescreatedinthecurrentpass.

HashJoin

TheHashJoiniteratorrequirestwoinputsets-theouterandinnertables.

TheHashJoiniteratorstartsbycreatingitsinnertableusingtheHashoperator.TheHashoperatorcreatesatemporaryHashindexthatcoversthejoincolumnintheinnertable.Whenthehashtable(thatis,theinnertable)iscreated,HashJoinreadseachrowintheoutertable,hashesthejoincolumn(fromtheoutertable),andsearchesthetemporaryHashindexforamatchingvalue.

InaGreenplumDatabaseinstance,aHashJoinalgorithmcanbeusedwiththefollowingjoinsemantics:

LeftJoin

LeftAntiSemiJoin

FullJoin

RightJoin

EXISTSJoin

ReverseInJoin

UniqueInnerJoin

UniqueOuterJoin

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

HashSpillBatches m1_name Batches Thecurrentbatchbeingspilled.

HashSpillTuples m2_name Tuples Thecurrentnumberofspilledtuples.

HashSpillBytes m3_name Bytes Thecurrentnumberofbytesspilledtodisk.

©CopyrightPivotalSoftwareInc,2013-2016 91 3.1.1

Page 92: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

HashAggregate

TheHashAggregateiteratorissimilartotheGroupAggregateiterator.AsingleinputsetisrequiredbytheHashAggregateiteratoranditcreatesahashtablefromtheinput.However,itdoesnotrequireitsinputtobeordered.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

AggregateTotalSpillTuples m1_name TuplesThenumberoftuplesspilledtodisk.

AggregateTotalSpillBytes m2_name Bytes Thenumberofbytesspilledtodisk.

AggregateTotalSpillBatches m3_name BatchesThenumberofspillbatchesrequired.

AggregateTotalSpillPass m4_name Passes Thenumberofpassesacrossallofthebatches.

AggregateCurrentSpillPassReadTuples

m5_name TuplesThenumberofbytesreadinforthisspillbatch

AggregateCurrentSpillPassReadBytes

m6_name BytesThenumberoftuplesreadinforthisspillbatch

AggregateCurrentSpillPassTuples m7_name TuplesThenumberoftuplesthatareineachspillfileinthecurrentpass.

AggregateCurrentSpillPassBytes m8_name BytesThenumberofbytesthatareineachspillfileinthecurrentpass.

AggregateCurrentSpillPassBatches

m9_name BatchesThenumberofbatchescreatedinthecurrentpass.

IndexScan

AnIndexScanoperatortraversesanindexstructure.Ifyouspecifyastartingvalueforanindexedcolumn,theIndexScanwillbeginattheappropriatevalue.Ifyouspecifyanendingvalue,theIndexScanwillcompleteassoonasitfindsanindexentrygreaterthantheendingvalue.AqueryplannerusesanIndexScanoperatorwhenitcanreducethesizeoftheresultsetbytraversingarangeofindexedvalues,orwhenitcanavoidasortbecauseoftheimplicitorderingofferedbyanindex.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

IndexScanRestore m1_name Restores Thenumberofrestores.

IndexScanRescan m2_name Rescans Thenumberofrescans.

Limit

TheLimitoperatorisusedtolimitthesizeofaresultset.AGreenplumDatabaseinstanceusestheLimitoperatorforbothLimitandOffsetprocessing.TheLimitoperatorworksbydiscardingthefirstxrowsfromitsinputset,returningthenextyrows,anddiscardingtheremainder.IfthequeryincludesanOFFSETclause,xrepresentstheoffsetamount;otherwise,xiszero.IfthequeryincludesaLIMITclause,yrepresentstheLimitamount;otherwise,yisatleastaslargeasthenumberofrowsintheinputset.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

Materialize

Thematerializeiteratorisusedforsomesub-selectoperations.Thequeryplannercandecidethatitislessexpensivetomaterializeasub-selectonetimethanitistorepeattheworkforeachtop-levelrow.Materializeisalsousedforsomemerge/joinoperations.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

MaterializeRescan m1_name Rescans Thenumberoftimestheexecutorrequestedtorescanthedateforthisiterator.

MergeJoin

TheMergeJoiniteratorjoinstwotables.LiketheNestedLoopiterator,MergeJoinrequirestwoinputsets:Anoutertableandaninnertable.Eachinput

©CopyrightPivotalSoftwareInc,2013-2016 92 3.1.1

Page 93: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

setmustbeorderedbythejoincolumns.InaGreenplumDatabaseinstance,theMergeJoinalgorithmcanbeusedwiththefollowingjoinsemantics:

LeftJoin

LeftAntiSemiJoin

FullJoin

RightJoin

EXISTSJoin

ReverseInJoin

UniqueOuterjoins

UniqueInnerJoin

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

MergeJoinInnerTuples m1_name TuplesThenumberofrowsfromtheinnerpartofthequeryplan.

MergeJoinOuterTuples m2_name TuplesThenumberofrowsfromtheOuterpartofthequeryplan.

NestedLoop

TheNestedLoopiteratorisusedtoperformajoinbetweentwotables,andasaresultrequirestwoinputsets.Itfetcheseachtablefromoneoftheinputsets(calledtheoutertable).Foreachrowintheoutertable,theotherinput(calledtheinnertable)issearchedforarowthatmeetsthejoinqualifier.InaGreenplumDatabaseinstance,aMergeJoinalgorithmcanbeusedwiththefollowingjoinsemantics:

LeftJoin

LeftAntiSemiJoin

FullJoin

RightJoin

EXISTSJoin

ReverseInJoin

UniqueOuterJoin

UniqueInnerJoin

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

NestedLoopInnerTuples m1_name Tuples Thenumberofrowsfromtheinnerpartofthequeryplan.

NestedLoopOuterTuples m2_name Tuples Thenumberofrowsfromtheouterpartofthequeryplan.

RedistributeMotion

Thisiteratorsendsanoutboundtupletoonlyonedestinationbasedonthevalueofahash.

NotethattheMotionmetricsfortheiteratorareusefulwheninvestigatingpotentialnetworkingissuesintheGreenplumDatabasesystem.Typically,the“AckTime”valuesshouldbeverysmall(microsecondsormilliseconds).Howeverifthe“AckTime”valuesareoneormoreseconds(particularlythe“MotionMinAckTime”metric),thenanetworkperformanceissuelikelyexists.

Also,iftherearealargenumberofpacketsbeingdroppedbecauseofqueueoverflow,youcanincreasethevalueforthe gp_interconnect_queue_depthsystemconfigurationparametertoimproveperformance.SeetheGreenplumDatabaseReferenceGuideformoreinformationaboutsystemconfigurationparameters.

Rowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

MotionBytesSent m1_name BytesThenumberofbytessentbytheiterator.

MotionTotalAckTime m2_name Microseconds

Thetotalamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

©CopyrightPivotalSoftwareInc,2013-2016 93 3.1.1

Page 94: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

MotionAverageAckTime m3_name Microseconds

Theaverageamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMaxAckTime m4_name Microseconds

Themaximumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionMinAckTime m5_name Microseconds

Theminimumamountoftimethattheiteratorwaitedforanacknowledgementaftersendingapacketofdata.

MotionCountResent m6_name Packets

Thetotalnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.

MotionMaxResent m7_name Packets

Themaximumnumberofpacketsthattheiteratordidnotacknowledgewhentheyfirstarrivedinthequeue.Thismetricisappliedonaperpacketbasis.Forexample,avalueof“10”indicatesthataparticularpacketdidnotgetacknowledgedbythisiterator10times,andthatthiswasthemaximumforthisiterator.

MotionBytesReceived m8_name BytesThenumberofbytesreceivedbytheiterator.

MotionCountDropped m9_name PacketsThenumberofpacketsdroppedbytheiteratorbecauseofbufferoverruns.

Result

TheResultiteratorisusedtoeither(1)executeaquerythatdoesnotretrievedatafromatable,orevaluatethepartsofaWHEREclausethatdonotdependondataretrievedfromatable.ItcanalsobeusedifthetopnodeinthequeryplanisanAppenditerator.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

Repeat

Thisiteratorrepeatseveryinputoperatoracertainnumberoftimes.Thisistypicallyusedforcertaingroupingoperations.

MetricDescriptionRowsin m0_name RowsThenumberoftuplesreceivedbytheiterator.

SeqScan

TheSeqScaniteratorscansheaptables,andisthemostbasicqueryiterator.Anysingle-tablequerycanbedonebyusingtheSeqScaniterator.SeqScanstartsatthebeginningofaheaptableandscanstotheendoftheheaptable.Foreachrowintheheaptable,SeqScanevaluatesthequeryconstraints(theWHEREclause).Iftheconstraintsaresatisfied,therequiredcolumnsareaddedtotheresultset.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

SeqScanPageStats m1_name Pages Thenumberofpagesscanned.

SeqScanRestorePos m2_name Restores Thenumberoftimestheexecutorrestoredthescanposition.

SeqScanRescan m3_name Rescans Thenumberoftimestheexecutorrequestedtorescanthedateforthisiterator.

SetOp

TherearefourSetOpiterators:

©CopyrightPivotalSoftwareInc,2013-2016 94 3.1.1

Page 95: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

Intersect

IntersectAll

Except

ExceptAll

Theseiteratorsareproducedonlywhenthequeryplannerencountersan INTERSECT , INTERSECTALL

, EXCEPT ,or EXCEPTALL

clause,respectively.

AllSetOpiteratorsrequiretwoinputsets.Theycombinetheinputsetsintoasortedlist,andthengroupsofidenticalrowsareidentified.Foreachgroup,theSetOpiteratorscountsthenumberofrowscontributedbyeachinputset,thenusesthecountstodeterminethenumberofrowstoaddtotheresultset.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

SharedScan

Thisiteratorevaluatesthecommonpartsofaqueryplan.Itsharestheoutputofthecommonsub-planswithallotheriterators,sothatthesub-planonlyneedstoexecuteonetime.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

SeqScanPageStats m1_name Pages Thenumberofpagesscanned.

SeqScanRestorePos m2_name Restores Thenumberoftimestheexecutorrestoredthescanposition.

SeqScanRescan m3_name Rescans Thenumberoftimestheexecutorrequestedtorescanthedateforthisiterator.

Sort

TheSortiteratorimposesanorderingontheresultset.AGreenplumDatabaseinstanceusestwodifferentsortstrategies:Anin-memorysortandanon-disksort.Ifthesizeoftheresultsetexceedstheavailablememory,theSortiteratordistributestheinputsettoacollectionofsortedworkfilesandthenmergestheworkfilesbacktogetheragain.Iftheresultsetislessthantheavailablememory,thesortisdoneinmemory.

TheSortiteratorisusedformanypurposes.ASortcanbeusedtosatisfyan ORDERBY clause.Also,somequeryoperatorsrequiretheirinputsetstobeordered.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

SortMemoryUsage m1_name Bytes Thenumberofbytesusedbythesort.

SortSpillTuples m2_name Tuples Thecurrentnumberofspilledtuples.

SortSpillBytes m3_name Bytes Thecurrentnumberofspilledbytes.

SortSpillPass m4_name Passes Thenumberofmergepasses.Eachmergepassmergesseveralsortedrunsintolargerruns.

SortCurrentSpillPassTuples m5_name Tuples Thenumberoftuplesspilledinthecurrentspillpass.

SortCurrentSpillPassBytes m6_name Bytes Thenumberofbytesspilledinthecurrentspillpass.

SubqueryScan

ASubqueryScaniteratorisapass-throughiterator.Itscansthroughitsinputset,addingeachrowtotheresultset.Thisiteratorisusedforinternalpurposesandhasnoaffectontheoverallqueryplan.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

SubqueryScanRescan m1_name Rescans Thenumberoftimestheexecutorrequestedtorescanthedateforthisiterator.

TidScan

TheTidScan(tupleIDscan)iteratorisusedwheneverthequeryplannerencountersaconstraintoftheform ctid=expression

or expression=ctid

.This

specifiesatupleID,anidentifierthatisuniquewithinatable.ThetupleIDworkslikeabookmark,butisvalidonlywithinasingletransaction.Afterthetransactioncompletes,thetupleIDisnotusedagain.

Metric MetricColumn Unit Description

©CopyrightPivotalSoftwareInc,2013-2016 95 3.1.1

Page 96: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.Metric MetricColumn Unit Description

Unique

TheUniqueiteratoreliminatesduplicatevaluesfromtheinputset.Theinputsetmustbeorderedbythecolumns,andthecolumnsmustbeunique.TheUniqueoperatorremovesonlyrows—itdoesnotremovecolumnsanditdoesnotchangetheorderingoftheresultset.Uniquecanreturnthefirstrowintheresultsetbeforeithasfinishedprocessingtheinputset.ThequeryplannerusestheUniqueoperatortosatisfya DISTINCT clause.Uniqueisalsousedtoeliminateduplicatesina UNION .

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

ValuesScan

TheValueScaniteratorisusedtoiterateoverasetofconstanttuples.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

Window

TheWindowfunctionperformscalculationsacrosssetsofrowsthatarerelatedtothecurrentqueryrow.TheWindowiteratorcomputesWindowfunctionsontheinputsetofrows.

Metric MetricColumn Unit Description

Rowsin m0_name Rows Thenumberoftuplesreceivedbytheiterator.

©CopyrightPivotalSoftwareInc,2013-2016 96 3.1.1

Page 97: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

log_alert_*The log_alert_* tablesstore pg_log errorsandwarnings.

Therearethree log_alert tables,eachwiththesamecolumns:

log_alert_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Current pg_log errorsandwarningsdataisstoredin log_alert_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandcommitmenttothelog_alert_history table.

log_alert_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforqueryworkloaddatathathasbeenclearedfrom log_alert_now buthasnotyetbeencommittedto log_alert_history .Ittypicallyonlycontainsafewminutesworthofdata.

log_alert_history isaregulartablethatstoreshistoricaldatabase-wideerrorsandwarningsdata.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

logtime timestampwithtimezone Timestampforthislog

loguser text Userofthequery

logdatabase text Theaccesseddatabase

logpid text Processid

logthread text Threadnumber

loghost text Hostnameoripaddress

logport text Portnumber

logsessiontime timestampwithtimezone Sessiontimestamp

logtransaction integer Transactionid

logsession text Sessionid

logcmdcount text Commandcount

logsegment text Segmentnumber

logslice text Slicenumber

logdistxact text Distributedtransaction

loglocalxact text Localtransaction

logsubxact text Subtransaction

logseverity text Logseverity

logstate text State

logmessage text Logmessage

logdetail text Detailedmessage

loghint text Hintinfo

logquery text Executedquery

logquerypos text Queryposition

logcontext text Contextinfo

logdebug text Debug

logcursorpos text Cursorposition

logfunction text Functioninfo

logfile text Sourcecodefile

logline text Sourcecodeline

logstack text Stacktrace

©CopyrightPivotalSoftwareInc,2013-2016 97 3.1.1

Page 98: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

LogProcessingandRotationTheGreenplumDatabasesystemloggerwritesalertlogsinthe $MASTER_DATA_DIRECTORY/gpperfmon/logs directory.

Theagentprocess( gpmmon )performsthefollowingstepstoconsolidatelogfilesandloadthemintothe gpperfmon database:

1. Gathersallofthe gpdb-alert-* filesinthelogsdirectory(exceptthelatest,whichthesysloggerhasopenandiswritingto)intoasinglefile,alert_log_stage .

2. Loadsthe alert_log_stage fileintothe log_alert_history tableinthe gpperfmon database.

3. Truncatesthe alert_log_stage file.

4. Removesallofthe gp-alert-* files,exceptthelatest.

Thesysloggerrotatesthealertlogevery24hoursorwhenthecurrentlogfilereachesorexceeds1MB.Arotatedlogfilecanexceed1MBifasingleerrormessagecontainsalargeSQLstatementoralargestacktrace.Also,thesysloggerprocesseserrormessagesinchunks,withaseparatechunkforeachloggingprocess.ThesizeofachunkisOS-dependent;onRedHatEnterpriseLinux,forexample,itis4096bytes.IfmanyGreenplumDatabasesessionsgenerateerrormessagesatthesametime,thelogfilecangrowsignificantlybeforeitssizeischeckedandlogrotationistriggered.

©CopyrightPivotalSoftwareInc,2013-2016 98 3.1.1

Page 99: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

queries_*The queries_* tablesstorehigh-levelquerystatusinformation.

The tmid , ssid and ccnt columnsarethecompositekeythatuniquelyidentifiesaparticularquery.Thesecolumnscanbeusedtojoinwiththeiterators_* tables.

Therearethreequeriestables,allhavingthesamecolumns:

queries_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentquerystatusisstoredinqueries_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttothe queries_historytable.

queries_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforquerystatusdatathathasbeenclearedfrom queries_now buthasnotyetbeencommittedto queries_history .Ittypicallyonlycontainsafewminutesworthofdata.

queries_history isaregulartablethatstoreshistoricalquerystatusdata.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

ctime timestamp Timethisrowwascreated.

tmid intAtimeidentifierforaparticularquery.Allrecordsassociatedwiththequerywillhavethesame tmid .

ssid intThesessionidasshownby gp_session_id .Allrecordsassociatedwiththequerywillhavethesame ssid .

ccnt int

Thecommandnumberwithinthissessionasshownby gp_command_count .Allrecordsassociatedwiththequerywillhavethesameccnt .

username varchar(64) Greenplumrolenamethatissuedthisquery.

db varchar(64) Nameofthedatabasequeried.

cost int Notimplementedinthisrelease.

tsubmit timestamp Timethequerywassubmitted.

tstart timestamp Timethequerywasstarted.

tfinish timestamp Timethequeryfinished.

status varchar(64)Statusofthequery– start , done ,or abort.

rows_out bigint Rowsoutforthequery.

cpu_elapsed bigint

CPUusagebyallprocessesacrossallsegmentsexecutingthisquery(inseconds).ItisthesumoftheCPUusagevaluestakenfromallactiveprimarysegmentsinthedatabasesystem.

NotethatGreenplumCommandCenterlogsthevalueas0ifthequeryruntimeisshorterthanthevalueforthequantum.Thisoccursevenifthequeryruntimeisgreaterthanthevaluesformin_query_time and min_detailed_query ,andthesevaluesarelowerthanthevalueforthequantum.

cpu_currpct float

CurrentCPUpercentaverageforallprocessesexecutingthisquery.Thepercentagesforallprocessesrunningoneachsegmentareaveraged,andthentheaverageofallthosevaluesiscalculatedtorenderthismetric.

©CopyrightPivotalSoftwareInc,2013-2016 99 3.1.1

Page 100: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

CurrentCPUpercentaverageisalwayszeroinhistoricalandtaildata.

skew_cpu float

Displaystheamountofprocessingskewinthesystemforthisquery.Processing/CPUskewoccurswhenonesegmentperformsadisproportionateamountofprocessingforaquery.ThisvalueisthecoefficientofvariationintheCPU%metricofalliteratorsacrossallsegmentsforthisquery,multipliedby100.Forexample,avalueof.95isshownas95.

skew_rows float

Displaystheamountofrowskewinthesystem.Rowskewoccurswhenonesegmentproducesadisproportionatenumberofrowsforaquery.Thisvalueisthecoefficientofvariationfortherows_in metricofalliteratorsacrossallsegmentsforthisquery,multipliedby100.Forexample,avalueof.95isshownas95.

query_hash bigint Notimplementedinthisrelease.

query_text text TheSQLtextofthisquery.

query_plan textTextofthequeryplan.Notimplementedinthisrelease.

application_name varchar(64) Thenameoftheapplication.

rsqname varchar(64) Thenameoftheresourcequeue.

rqppriority varchar(64)Thepriorityofthequery–max, high, med, low, or min .

©CopyrightPivotalSoftwareInc,2013-2016 100 3.1.1

Page 101: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

segment_*The segment_* tablescontainmemoryallocationstatisticsfortheGreenplumDatabasesegmentinstances.Thistrackstheamountofmemoryconsumedbyallpostgresprocessesofaparticularsegmentinstance,andtheremainingamountofmemoryavailabletoasegmentasperthesettingofthepostgresql.conf configurationparameter: gp_vmem_protect_limit .Queryprocessesthatcauseasegmenttoexceedthislimitwillbecancelledinordertopreventsystem-levelout-of-memoryerrors.SeetheGreenplumDatabaseReferenceGuideformoreinformationaboutthisparameter.

Therearethreesegmenttables,allhavingthesamecolumns:

segment_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentmemoryallocationdataisstoredin segment_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttothesegment_historytable.

segment_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableformemoryallocationdatathathasbeenclearedfrom segment_now buthasnotyetbeencommittedto segment_history .Ittypicallyonlycontainsafewminutesworthofdata.

segment_history isaregulartablethatstoreshistoricalmemoryallocationmetrics.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Aparticularsegmentinstanceisidentifiedbyits hostname and dbid (theuniquesegmentidentifierasperthe gp_segment_configuration systemcatalogtable).

ctime

timestamp(0)

(withouttimezone)Thetimetherowwascreated.

dbid intThesegmentID( dbid fromgp_segment_configuration ).

hostname charvar(64) Thesegmenthostname.

dynamic_memory_used bigintTheamountofdynamicmemory(inbytes)allocatedtoqueryprocessesrunningonthissegment.

dynamic_memory_available bigint

Theamountofadditionaldynamicmemory(inbytes)thatthesegmentcanrequestbeforereachingthelimitsetbythegp_vmem_protect_limit parameter.

Seealsotheviews memory_info and dynamic_memory_info foraggregatedmemoryallocationandutilizationbyhost.

©CopyrightPivotalSoftwareInc,2013-2016 101 3.1.1

Page 102: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

socket_stats_*The socket_stats_* tablesstorestatisticalmetricsaboutsocketusageforaGreenplumDatabaseinstance.Therearethreesystemtables,allhavingthesamecolumns:

Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

socket_stats_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .

socket_stats_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforsocketstatisticalmetricsthathasbeenclearedfrom socket_stats_now buthasnotyetbeencommittedto socket_stats_history .Ittypicallyonlycontainsafewminutesworthofdata.

socket_stats_history isaregulartablethatstoreshistoricalsocketstatisticalmetrics.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

total_sockets_used int Totalsocketsusedinthesystem.

tcp_sockets_inuse int NumberofTCPsocketsinuse.

tcp_sockets_orphan int NumberofTCPsocketsorphaned.

tcp_sockets_timewait int NumberofTCPsocketsinTime-Wait.

tcp_sockets_alloc int NumberofTCPsocketsallocated.

tcp_sockets_memusage_inbytes int AmountofmemoryconsumedbyTCPsockets.

udp_sockets_inuse int NumberofUDPsocketsinuse.

udp_sockets_memusage_inbytes int AmountofmemoryconsumedbyUDPsockets.

raw_sockets_inuse int NumberofRAWsocketsinuse.

frag_sockets_inuse int NumberofFRAGsocketsinuse.

frag_sockets_memusage_inbytes int AmountofmemoryconsumedbyFRAGsockets.

©CopyrightPivotalSoftwareInc,2013-2016 102 3.1.1

Page 103: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

system_*The system_* tablesstoresystemutilizationmetrics.Therearethreesystemtables,allhavingthesamecolumns:

system_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Currentsystemutilizationdataisstoredin system_now duringtheperiodbetweendatacollectionfromtheCommandCenteragentsandautomaticcommitmenttothe system_historytable.

system_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .Thisisatransitionaltableforsystemutilizationdatathathasbeenclearedfrom system_now buthasnotyetbeencommittedto system_history .Ittypicallyonlycontainsafewminutesworthofdata.

system_history isaregulartablethatstoreshistoricalsystemutilizationmetrics.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

ctime timestamp Timethisrowwascreated.

hostname varchar(64) Segmentormasterhostnameassociatedwiththesesystemmetrics.

mem_total bigint TotalsystemmemoryinBytesforthishost.

mem_used bigint UsedsystemmemoryinBytesforthishost.

mem_actual_used bigint UsedactualmemoryinBytesforthishost(notincludingthememoryreservedforcacheandbuffers).

mem_actual_free bigint FreeactualmemoryinBytesforthishost(notincludingthememoryreservedforcacheandbuffers).

swap_total bigint TotalswapspaceinBytesforthishost.

swap_used bigint UsedswapspaceinBytesforthishost.

swap_page_in bigint Numberofswappagesin.

swap_page_out bigint Numberofswappagesout.

cpu_user float CPUusagebytheGreenplumsystemuser.

cpu_sys float CPUusageforthishost.

cpu_idle float IdleCPUcapacityatmetriccollectiontime.

load0 float CPUloadaverageforthepriorone-minuteperiod.

load1 float CPUloadaverageforthepriorfive-minuteperiod.

load2 float CPUloadaverageforthepriorfifteen-minuteperiod.

quantum int Intervalbetweenmetriccollectionforthismetricentry.

disk_ro_rate bigint Diskreadoperationspersecond.

disk_wo_rate bigint Diskwriteoperationspersecond.

disk_rb_rate bigint Bytespersecondfordiskwriteoperations.

net_rp_rate bigint Packetspersecondonthesystemnetworkforreadoperations.

net_wp_rate bigint Packetspersecondonthesystemnetworkforwriteoperations.

net_rb_rate bigint Bytespersecondonthesystemnetworkforreadoperations.

net_wb_rate bigint Bytespersecondonthesystemnetworkforwriteoperations.

©CopyrightPivotalSoftwareInc,2013-2016 103 3.1.1

Page 104: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

tcp_stats_*The tcp_stats_* tablesstorestatisticalmetricsaboutTCPcommunicationsforaGreenplumDatabaseinstance.

Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

Therearethreesystemtables,allhavingthesamecolumns:

tcp_stats_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .

tcp_stats_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .ThisisatransitionaltableforTCPstatisticaldatathathasbeenclearedfrom tcp_stats_now buthasnotyetbeencommittedto tcp_stats_history .Ittypicallyonlycontainsafewminutesworthofdata.

tcp_stats_history isaregulartablethatstoreshistoricalTCPstatisticaldata.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

segments_received bigint NumberofTCPsegmentsreceived.

segments_sent bigint NumberofTCPsegmentssent.

segments_retransmitted bigint NumberofTCPsegmentsretransmitted.

active_connections int NumberofactiveTCPconnections.

passive_connections int NumberofpassiveTCPconnections.

failed_connection_attempts int NumberoffailedTCPconnectionattempts.

connections_established int NumberofTCPconnectionsestablished.

connection_resets_received int NumberofTCPconnectionresetsreceived.

connection_resets_sent int NumberofTCPconnectionresetssent.

©CopyrightPivotalSoftwareInc,2013-2016 104 3.1.1

Page 105: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

udp_stats_*The udp_stats_* tablesstorestatisticalmetricsaboutUDPcommunicationsforaGreenplumDatabaseinstance.

Thesetablesareinplaceforfutureuseandarenotcurrentlypopulated.

Therearethreesystemtables,allhavingthesamecolumns:

udp_stats_now isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .

udp_stats_tail isanexternaltablewhosedatafilesarestoredin $MASTER_DATA_DIRECTORY/gpperfmon/data .ThisisatransitionaltableforUDPstatisticaldatathathasbeenclearedfrom udp_stats_now buthasnotyetbeencommittedto udp_stats_history .Ittypicallyonlycontainsafewminutesworthofdata.

udp_stats_history isaregulartablethatstoreshistoricalUDPstatisticalmetrics.Itispre-partitionedintomonthlypartitions.Partitionsareautomaticallyaddedintwomonthincrementsasneeded.Administratorsmustdropoldpartitionsforthemonthsthatarenolongerneeded.

Column Type Description

packets_received bigint NumberofUDPpacketsreceived.

packets_sent bigint NumberofUDPpacketssent.

packets_received_unknown_port int NumberofUDPpacketsreceivedonunknownports.

packet_receive_errors bigint NumberoferrorsencounteredduringUDPpacketreceive.

©CopyrightPivotalSoftwareInc,2013-2016 105 3.1.1

Page 106: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

iterators_*_rollupThe iterators_*_rollup setofviewsaggregatethemetricsstoredinthe iterators_* tables.Aqueryiteratorreferstoanodeoroperationinaqueryplan.Forexample,asequentialscanoperationmaybeonetypeofiteratorinaparticularqueryplan.Foreachiteratorinaqueryplan,the iterators_* tablesstorethemetricscollectedfromeachsegmentinstance.The iterators_*_rollup viewssummarizethequeryiteratormetricsacrossallsegmentsinthesystem.

The tmid , ssid and ccnt columnsarethecompositekeythatuniquelyidentifiesaparticularquery.

Therearethreeiteratorsrollupviews,allhavingthesamecolumns:

The iterators_now_rollup viewshowsiteratordatafromthe interators_now tableaggregatedacrossallsegmentsinthesystem.

The iterators_tail_rollup viewshowsiteratordatafromthe interators_tail tableaggregatedacrossallsegmentsinthesystem.

The iterators_history_rollup showsiteratordatafromthe interators_history tableaggregatedacrossallsegmentsinthesystem.

Seealsothe iterators_* tablesformoreinformationaboutthequeryplaniteratortypesandthemetricscollectedforeachiterator.

sample_time timestampThe ctime fromtheassociated iterators_*

table.

tmid intAtimeidentifierforaparticularquery.Alliteratorrecordsassociatedwiththequerywillhavethesame tmid .

ssid intThesessionidasshownbythe gp_session_idparameter.Alliteratorrecordsassociatedwiththequerywillhavethesame ssid .

ccnt int

Thecommandnumberwithinthissessionasshownby gp_command_count parameter.Alliteratorrecordsassociatedwiththequerywillhavethesame ccnt .

nid intTheIDofthisqueryplannodefromthesliceplan.

pnid intThe pnid (sliceplanparentnodeID)fromtheassociated iterators_* table.

ntype textThe ntype (node/iteratortype)fromtheassociated iterators_* table.

nstatus textTheaccumulatedstatusofthisiterator.Possiblevaluesare:Initialize,Executing,orFinished.

tstart timestamp Theaveragestarttimeforthisiterator.

tduration numeric Theaverageexecutiontimeforthisiterator.

pmemsize numericTheaverageworkmemoryallocatedbytheGreenplumplannertothisiterator’squeryprocesses.

pmemmax numericTheaverageofthemaximumplannerworkmemoryusedbythisiterator’squeryprocesses.

memsize numericTheaverageOSmemoryallocatedtothisiterator’sprocesses.

memresid numericTheaverageresidentmemoryallocatedtothisiterator’sprocesses(asopposedtosharedmemory).

memshare numericTheaveragesharedmemoryallocatedtothisiterator’sprocesses.

cpu_elapsed numericSumoftheCPUusageofallsegmentprocessesexecutingthisiterator.

ThecurrentaveragepercentageofCPUutilizationusedbythisiterator’sprocesses.This

©CopyrightPivotalSoftwareInc,2013-2016 106 3.1.1

Page 107: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

cpu_currpct doubleprecisionutilizationusedbythisiterator’sprocesses.Thisvalueisalwayszeroforhistorical(completed)iterators.

rows_out numericThetotalnumberofactualrowsoutputforthisiteratoronallsegments.

rows_out_est numericThetotalnumberofoutputrowsforallsegmentsasestimatedbythequeryplanner.

skew_cpu numeric

Coefficientofvariationfor cpu_elapsed ofiteratorsacrossallsegmentsforthisquery,multipliedby100.Forexample,avalueof.95isrenderedas95.

skew_rows numeric

Coefficientofvariationfor rows_out ofiteratorsacrossallsegmentsforthisquery,multipliedby100.Forexample,avalueof.95is

renderedas95.

m0 text

Thename( m0_name ),unitofmeasure(m0_unit) ,averageactualvalue( m0_val ),andaverageestimatedvalue( m0_est )forthisiteratormetricacrossallsegments.The m0metricisalwaysrowsforalliteratortypes.

m1 text

Thename( m1_name ),unitofmeasure(m1_unit ),averageactualvalue( m1_val ),andaverageestimatedvalue( m1_est )forthisiteratormetricacrossallsegments.

m2 text

Thename( m2_name ),unitofmeasure(m2_unit ),averageactualvalue( m2_val ),andaverageestimatedvalue( m2_est )forthisiteratormetricacrossallsegments.

m3 text

Thename( m3_name ),unitofmeasure(m3_unit ),averageactualvalue( m3_val ),andaverageestimatedvalue( m3_est )forthisiteratormetricacrossallsegments.

m4 text

Thename( m4_name ),unitofmeasure(m4_unit ),averageactualvalue( m4_val ),andaverageestimatedvalue( m4_est )forthisiteratormetricacrossallsegments.

m5 text

Thename( m5_name ),unitofmeasure(m5_unit ),averageactualvalue( m5_val ),andaverageestimatedvalue( m5_est )forthisiteratormetricacrossallsegments.

m6 text

Thename( m6_name ),unitofmeasure(m6_unit ),averageactualvalue( m6_val ),andaverageestimatedvalue( m6_est )forthisiteratormetricacrossallsegments.

m7 text

Thename( m7_name ),unitofmeasure(m7_unit ),averageactualvalue( m7_val ),andaverageestimatedvalue( m7_est )forthisiteratormetricacrossallsegments.

m8 text

Thename( m8_name ),unitofmeasure(m8_unit ),averageactualvalue( m8_val ),

andaverageestimatedvalue( m8_est )forthisiteratormetricacrossallsegments.

m9 text

Thename( m9_name ),unitofmeasure(m9_unit ),averageactualvalue( m9_val ),andaverageestimatedvalue( m9_est )forthisiteratormetricacrossallsegments.

m10 - m5 textMetrics m10 through m15 arenotcurrentlyusedbyanyiteratortypes.

©CopyrightPivotalSoftwareInc,2013-2016 107 3.1.1

Page 108: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

t0 text

Thenameoftherelation( t0_val )beingscannedbythisiterator.Thismetriciscollectedonlyforiteratorsthatperformscanoperationssuchasasequentialscanorfunctionscan.

©CopyrightPivotalSoftwareInc,2013-2016 108 3.1.1

Page 109: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

dynamic_memory_infoThe dynamic_memory_info viewshowsasumoftheusedandavailabledynamicmemoryforallsegmentinstancesonasegmenthost.DynamicmemoryreferstothemaximumamountofmemorythatGreenplumDatabaseinstancewillallowthequeryprocessesofasinglesegmentinstancetoconsumebeforeitstartscancellingprocesses.Thislimitissetbythe gp_vmem_protect_limit serverconfigurationparameter,andisevaluatedonaper-segmentbasis.

Column Type Description

ctime

timestamp(0)withouttimezone

Timethisrowwascreatedinthe segment_history table.

hostname varchar(64) Segmentormasterhostnameassociatedwiththesesystemmemorymetrics.

dynamic_memory_used_mb numeric TheamountofdynamicmemoryinMBallocatedtoqueryprocessesrunningonthissegment.

dynamic_memory_available_mb numeric

Theamountofadditionaldynamicmemory(inMB)availabletothequeryprocessesrunningonthissegmenthost.Notethatthisvalueisasumoftheavailablememoryforallsegmentsonahost.Eventhoughthisvaluereportsavailablememory,itispossiblethatoneormoresegmentsonthehosthaveexceededtheirmemorylimitassetbythe gp_vmem_protect_limit parameter.

©CopyrightPivotalSoftwareInc,2013-2016 109 3.1.1

Page 110: Table of Contents - Pivotal GPCC Docs · Pivotal Greenplum Command Center is a management tool for the Greenplum Big Data Platform. This section introduces key concepts about Greenplum

memory_infoThe memory_info viewshowsper-hostmemoryinformationfromthe system_history and segment_history tables.Thisallowsadministratorstocomparethetotalmemoryavailableonasegmenthost,totalmemoryusedonasegmenthost,anddynamicmemoryusedbyqueryprocesses.

Column Type Description

ctime

timestamp(0)withouttimezone

Timethisrowwascreatedinthe segment_history table.

hostname varchar(64) Segmentormasterhostnameassociatedwiththesesystemmemorymetrics.

mem_total_mb numeric TotalsystemmemoryinMBforthissegmenthost.

mem_used_mb numeric TotalsystemmemoryusedinMBforthissegmenthost.

mem_actual_used_mb numeric ActualsystemmemoryusedinMBforthissegmenthost.

mem_actual_free_mb numeric ActualsystemmemoryfreeinMBforthissegmenthost.

swap_total_mb numeric TotalswapspaceinMBforthissegmenthost.

swap_used_mb numeric TotalswapspaceusedinMBforthissegmenthost.

dynamic_memory_used_mb numeric TheamountofdynamicmemoryinMBallocatedtoqueryprocessesrunningonthissegment.

dynamic_memory_available_mb numeric

Theamountofadditionaldynamicmemory(inMB)availabletothequeryprocessesrunningonthissegmenthost.Notethatthisvalueisasumoftheavailablememoryforallsegmentsonahost.Eventhoughthisvaluereportsavailablememory,itispossiblethatoneormoresegmentsonthehosthaveexceededtheirmemorylimitassetbythe gp_vmem_protect_limit parameter.

©CopyrightPivotalSoftwareInc,2013-2016 110 3.1.1