GreenPlum数据库启动关闭及数据库状态检查
Jan142016
本篇文章主要记录GreenPlum数据库的启动、关闭及状态查询。GreenPlum数据库提供gpstart和gpstop脚本来启动和关闭数据库，可以通过—help参数来查看这些脚本的帮助信息。
[gpadmin@mdw master]$ gpstart --help
COMMAND NAME: gpstart
Starts a Greenplum Database system.
*****************************************************
SYNOPSIS
*****************************************************
gpstart [-d <master_data_directory>] [-B <parallel_processes>]
[-R] [-m] [-y] [-a] [-t <timeout_seconds>]
[-l logfile_directory] [-v | -q]
gpstart -? | -h | --help
gpstart --version
*****************************************************
DESCRIPTION
*****************************************************
The gpstart utility is used to start the Greenplum Database server
processes. When you start a Greenplum Database system, you are
actually starting several postgres database server listener processes
at once (the master and all of the segment instances). The gpstart utility
handles the startup of the individual instances. Each instance is started
in parallel.
The first time an administrator runs gpstart, the utility creates a hosts
cache file named .gphostcache in the user's home directory. Subsequently,
the utility uses this list of hosts to start the system more efficiently.
If new hosts are added to the system, you must manually remove this file
from the gpadmin user's home directory. The utility will create a new hosts
cache file at the next startup.
Before you can start a Greenplum Database system, you must have initialized
the system using gpinitsystem first.
*****************************************************
OPTIONS
*****************************************************
-a (do not prompt)
Do not prompt the user for confirmation.
-B <parallel_processes>
The number of segments to start in parallel. If not specified,
the utility will start up to 64 parallel processes depending on
how many segment instances it needs to start.
-d <master_data_directory>
Optional. The master host data directory. If not specified,
the value set for $MASTER_DATA_DIRECTORY will be used.
-l <logfile_directory>
The directory to write the log file. Defaults to ~/gpAdminLogs.
-m (master only)
Optional. Starts the master instance only, which may be necessary
for maintenance tasks. This mode only allows connections to the master
in utility mode. For example:
PGOPTIONS='-c gp_session_role=utility' psql
Note that starting the system in master-only mode is only advisable
under supervision of Greenplum support. Improper use of this option
may lead to a split-brain condition and possible data loss.
-q (no screen output)
Run in quiet mode. Command output is not displayed on the screen,
but is still written to the log file.
-R (restricted mode)
Starts Greenplum Database in restricted mode (only database superusers
are allowed to connect).
-t | --timeout <number_of_seconds>
Specifies a timeout in seconds to wait for a segment instance to
start up. If a segment instance was shutdown abnormally (due to
power failure or killing its postgres database listener process,
for example), it may take longer to start up due to the database
recovery and validation process. If not specified, the default timeout
is 60 seconds.
-v (verbose output)
Displays detailed status, progress and error messages output by the utility.
-y (do not start standby master)
Optional. Do not start the standby master host. The default is to start
the standby master host and synchronization process.
-? | -h | --help (help)
Displays the online help.
--version (show utility version)
Displays the version of this utility.
*****************************************************
EXAMPLES
*****************************************************
Start a Greenplum Database system:
gpstart
Start a Greenplum Database system in restricted mode
(only allow superuser connections):
gpstart -R
Start the Greenplum master instance only and connect in utility mode:
gpstart -m
PGOPTIONS='-c gp_session_role=utility' psql
Display the online help for the gpstart utility:
gpstart -?
*****************************************************
SEE ALSO
*****************************************************
gpinitsystem, gpstop
常用的启动参数有以下几个参数：
-a，该模式不需要在启动过程中输入Y进行确认，将直接启动数据库。
-m，只启动Master节点，不启动Segment节点，通常在维护的时候使用。
-y，只启动Master的primary节点，不启动standby节点。
如下为GreenPlum数据库的启动过程。
[gpadmin@mdw gpdb]$ gpstart -a 20160114:10:56:18:013983 gpstart:mdw:gpadmin-[INFO]:-Starting gpstart with args: -a 20160114:10:56:18:013983 gpstart:mdw:gpadmin-[INFO]:-Gathering information and validating the environment... 20160114:10:56:18:013983 gpstart:mdw:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 4.3.6.2 build 1' 20160114:10:56:18:013983 gpstart:mdw:gpadmin-[INFO]:-Greenplum Catalog Version: '201310150' 20160114:10:56:18:013983 gpstart:mdw:gpadmin-[INFO]:-Starting Master instance in admin mode 20160114:10:56:19:013983 gpstart:mdw:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information 20160114:10:56:19:013983 gpstart:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160114:10:56:19:013983 gpstart:mdw:gpadmin-[INFO]:-Setting new master era 20160114:10:56:19:013983 gpstart:mdw:gpadmin-[INFO]:-Master Started... 20160114:10:56:19:013983 gpstart:mdw:gpadmin-[INFO]:-Shutting down master 20160114:10:56:21:013983 gpstart:mdw:gpadmin-[INFO]:-Commencing parallel segment instance startup, please wait 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:-Process results... 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:- Successful segment starts = 3 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:- Failed segment starts = 0 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:- Skipped segment starts (segments are marked down in configuration) = 0 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:- 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:-Successfully started 3 of 3 segment instances 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:23:013983 gpstart:mdw:gpadmin-[INFO]:-Starting Master instance mdw directory /gpdb/gpdata/master/gpseg-1 20160114:10:56:24:013983 gpstart:mdw:gpadmin-[INFO]:-Command pg_ctl reports Master mdw instance active 20160114:10:56:24:013983 gpstart:mdw:gpadmin-[INFO]:-No standby master configured. skipping... 20160114:10:56:24:013983 gpstart:mdw:gpadmin-[INFO]:-Database successfully started
可以通过gpstate脚本来查看数据库的状态信息，该命令的帮助信息如下：
[gpadmin@mdw master]$ gpstate --help
\COMMAND NAME: gpstate
Shows the status of a running Greenplum Database system.
*****************************************************
SYNOPSIS
*****************************************************
gpstate [-d <master_data_directory>] [-B <parallel_processes>]
[-s | -b | -Q | -e] [-m | -c] [-p] [-i] [-f]
[-v | -q] [-l <log_directory>]
gpstate -? | -h | --help
*****************************************************
DESCRIPTION
*****************************************************
The gpstate utility displays information about a running
Greenplum Database instance. There is additional information
you may want to know about a Greenplum Database system, since
it is comprised of multiple PostgreSQL database instances (segments)
spanning multiple machines. The gpstate utility provides
additional status information for a Greenplum Database system,
such as:
* Which segments are down.
* Master and segment configuration information (hosts,
data directories, etc.).
* The ports used by the system.
* A mapping of primary segments to their corresponding
mirror segments.
*****************************************************
OPTIONS
*****************************************************
-b (brief status)
Optional. Display a brief summary of the state of the
Greenplum Database system. This is the default option.
-B <parallel_processes>
The number of segments to check in parallel. If not specified,
the utility will start up to 60 parallel processes depending on
how many segment instances it needs to check.
-c (show primary to mirror mappings)
Optional. Display mapping of primary segments to their
corresponding mirror segments.
-d <master_data_directory>
Optional. The master data directory. If not specified, the
value set for $MASTER_DATA_DIRECTORY will be used.
-e (show segments with mirror status issues)
Show details on primary/mirror segment pairs that have
potential issues such as 1) the active segment is running in
change tracking mode, meaning a segment is down 2) the active
segment is in resynchronization mode, meaning it is catching
up changes to the mirror 3) a segment is not in its preferred role,
for example a segment that was a primary at system initialization
time is now acting as a mirror, meaning you may have one or more
segment hosts with unbalanced processing load.
-f (show standby master details)
Display details of the standby master host if configured.
-i (show Greenplum Database version)
Display the Greenplum Database software version information
for each instance.
-l <logfile_directory>
The directory to write the log file. Defaults to ~/gpAdminLogs.
-m (list mirrors)
Optional. List the mirror segment instances in the system,
their current role, and synchronization status.
-p (show ports)
List the port numbers used throughout the Greenplum Database
system.
-q (no screen output)
Optional. Run in quiet mode. Except for warning messages, command
output is not displayed on the screen. However, this information
is still written to the log file.
-Q (quick status)
Optional. Checks segment status in the system catalog on
the master host. Does not poll the segments for status.
-s (detailed status)
Optional. Displays detailed status information for the
Greenplum Database system.
-v (verbose output)
Optional. Displays error messages and outputs detailed status
and progress information.
-? | -h | --help (help)
Displays the online help.
*****************************************************
OUTPUT DEFINITIONS FOR DETAIL VIEW
*****************************************************
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
MASTER OUTPUT DATA
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
* Master host - host name of the master
* Master postgres process ID - PID of the master postgres database
listener process
* Master data directory - file system location of the master data directory
* Master port - port of the master database listener process
* Master current role - dispatch = regular operating mode
utility = maintenance mode
* Greenplum array configuration type - Standard = one NIC per host
Multi-Home = multiple NICs per host
* Greenplum initsystem version - version of Greenplum Database when
system was first initialized
* Greenplum current version - current version of Greenplum Database
* Postgres version - version of PostgreSQL that Greenplum Database
is based on
* Greenplum mirroring status - physical mirroring, SAN or none
* Master standby - host name of the standby master
* Standby master state - status of the standby master: active or passive
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SEGMENT OUTPUT DATA
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
* Hostname - system-configured host name
* Address - network address host name (NIC name)
* Datadir - file system location of segment data directory
* Port - port number of segment postgres database listener process
* Current Role - current role of a segment: Mirror or Primary
* Preferred Role - role at system initialization time: Mirror or Primary
* Mirror Status - status of a primary/mirror segment pair:
Synchronized = data is up to date on both
Resynchronizing = data is currently being copied from one to the other
Change Tracking = segment down and active segment is logging changes
* Change tracking data size - when in Change Tracking mode, the size of the change
log file (may grow and shrink as compression is applied)
* Estimated total data to synchronize - when in Resynchronization mode, the estimated
size of data left to syncronize
* Data synchronized - when in Resynchronization mode, the estimated size of data
that has already been syncronized
* Estimated resync progress with mirror - when in Resynchronization mode, the
estimated percentage of completion
* Estimated resync end time - when in Resynchronization mode, the estimated
time to complete
* File postmaster.pid - status of postmaster.pid lock file: Found or Missing
* PID from postmaster.pid file - PID found in the postmaster.pid file
* Lock files in /tmp - a segment port lock file for its postgres process is
created in /tmp (file is removed when a segment shuts down)
* Active PID - active process ID of a segment
* Master reports status as - segment status as reported in the system catalog:
Up or Down
Database status - status of Greenplum Database to incoming requests:
Up, Down, or Suspended. A Suspended state means database
activity is temporarily paused while a segment transitions from
one state to another.
*****************************************************
EXAMPLES
*****************************************************
Show detailed status information of a Greenplum Database system:
gpstate -s
Do a quick check for down segments in the master host system catalog:
gpstate -Q
Show information about mirror segment instances:
gpstate -m
Show information about the standby master configuration:
gpstate -f
Display the Greenplum software version information:
gpstate -i
*****************************************************
SEE ALSO
*****************************************************
\
常用的参数如下：
-s，详细信息。
-m，Mirror信息。
-f，Master的Standby信息。
-e，Segment的Mirror信息。
-i，版本信息。
如下为数据库启动状态通过gpstate –s查询的数据库状态信息。
[gpadmin@mdw gpdb]$ gpstate -s 20160114:10:56:40:014082 gpstate:mdw:gpadmin-[INFO]:-Starting gpstate with args: -s 20160114:10:56:40:014082 gpstate:mdw:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.6.2 build 1' 20160114:10:56:40:014082 gpstate:mdw:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.6.2 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Nov 12 2015 23:50:28' 20160114:10:56:40:014082 gpstate:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160114:10:56:40:014082 gpstate:mdw:gpadmin-[INFO]:-Gathering data from segments... . 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:--Master Configuration & Status 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Master host = mdw 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Master postgres process ID = 14042 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Master data directory = /gpdb/gpdata/master/gpseg-1 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Master port = 5432 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Master current role = dispatch 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Greenplum initsystem version = 4.3.6.2 build 1 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Greenplum current version = PostgreSQL 8.2.15 (Greenplum Database 4.3.6.2 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on Nov 12 2015 23:50:28 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Postgres version = 8.2.15 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Master standby = No master standby configured 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:-Segment Instance Status Report 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Segment Info 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Hostname = sdw1 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Address = sdw1 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Datadir = /gpdb/gpdata/primary/gpseg0 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Port = 40000 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Status 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- PID = 17195 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Configuration reports status as = Up 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Database status = Up 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Segment Info 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Hostname = sdw2 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Address = sdw2 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Datadir = /gpdb/gpdata/primary/gpseg1 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Port = 40000 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Status 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- PID = 17111 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Configuration reports status as = Up 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Database status = Up 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Segment Info 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Hostname = sdw3 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Address = sdw3 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Datadir = /gpdb/gpdata/primary/gpseg2 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Port = 40000 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Status 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- PID = 23033 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Configuration reports status as = Up 20160114:10:56:41:014082 gpstate:mdw:gpadmin-[INFO]:- Database status = Up
gpstop脚本用来关闭、重启、加载新修改的参数以至生效等功能，下面是gpstop命令的帮助信息。
[gpadmin@mdw master]$ gpstop --help
COMMAND NAME: gpstop
Stops or restarts a Greenplum Database system.
*****************************************************
SYNOPSIS
*****************************************************
gpstop [-d <master_data_directory>] [-B <parallel_processes>]
[-M smart | fast | immediate] [-t <timeout_seconds>]
[-r] [-y] [-a] [-l <logfile_directory>] [-v | -q]
gpstop -m [-d <master_data_directory>] [-y] [-l <logfile_directory>]
[-v | -q]
gpstop -u [-d <master_data_directory>] [-l <logfile_directory>]
[-v | -q]
gpstop --version
gpstop -? | -h | --help
*****************************************************
DESCRIPTION
*****************************************************
The gpstop utility is used to stop the database servers that
comprise a Greenplum Database system. When you stop a Greenplum
Database system, you are actually stopping several postgres
database server processes at once (the master and all of the
segment instances). The gpstop utility handles the shutdown
of the individual instances. Each instance is shutdown in parallel.
By default, you are not allowed to shut down Greenplum Database
if there are any client connections to the database. Use
the -M fast option to roll back and terminate any connections
before shutting down. If there are any transactions in progress,
the default behavior is to wait for them to commit before
shutting down. Use the -M fast option to roll back open
transactions.
With the -u option, the utility uploads changes made to the
master pg_hba.conf file or to runtime configuration parameters
in the master postgresql.conf file without interruption of
service. Note that any active sessions will not pickup the
changes until they reconnect to the database.
*****************************************************
OPTIONS
*****************************************************
-a (do not prompt)
Do not prompt the user for confirmation.
-B <parallel_processes>
The number of segments to stop in parallel. If not specified,
the utility will start up to 64 parallel processes depending
on how many segment instances it needs to stop.
-d <master_data_directory>
Optional. The master host data directory. If not specified,
the value set for $MASTER_DATA_DIRECTORY will be used.
-l <logfile_directory>
The directory to write the log file. Defaults to ~/gpAdminLogs.
-m (master only)
Optional. Shuts down a Greenplum master instance that was
started in maintenance mode.
-M fast (fast shutdown - rollback)
Fast shut down. Any transactions in progress are interrupted and rolled back.
-M immediate (immediate shutdown - abort)
Immediate shut down. Any transactions in progress are aborted. This
shutdown mode is not recommended, and in some circumstances can cause
database corruption requiring manual recovery.
This mode kills all postgres processes without allowing the database
server to complete transaction processing or clean up any temporary or
in-process work files.
-M smart (smart shutdown - warn)
Smart shut down. If there are active connections, this command
fails with a warning. This is the default shutdown mode.
-q (no screen output)
Run in quiet mode. Command output is not displayed on the
screen, but is still written to the log file.
-r (restart)
Restart after shutdown is complete.
-t <timeout_seconds>
Specifies a timeout threshold (in seconds) to wait for a
segment instance to shutdown. If a segment instance does not
shutdown in the specified number of seconds, gpstop displays
a message indicating that one or more segments are still in
the process of shutting down and that you cannot restart
Greenplum Database until the segment instance(s) are stopped.
This option is useful in situations where gpstop is executed
and there are very large transactions that need to rollback.
These large transactions can take over a minute to rollback
and surpass the default timeout period of 600 seconds.
-u (reload pg_hba.conf and postgresql.conf files only)
This option reloads the pg_hba.conf files of the master and
segments and the runtime parameters of the postgresql.conf files
but does not shutdown the Greenplum Database array. Use this
option to make new configuration settings active after editing
postgresql.conf or pg_hba.conf. Note that this only applies to
configuration parameters that are designated as runtime parameters.
-v (verbose output)
Displays detailed status, progress and error messages output
by the utility.
--version (show utility version)
Displays the version of this utility.
-y (do not stop standby master)
Do not stop the standby master process. The default is to stop the standby master.
-? | -h | --help (help)
Displays the online help.
*****************************************************
EXAMPLES
*****************************************************
Stop a Greenplum Database system in smart mode:
gpstop
Stop a Greenplum Database system in fast mode:
gpstop -M fast
Stop all segment instances and then restart the system:
gpstop -r
Stop a master instance that was started in maintenance mode:
gpstop -m
Reload the postgresql.conf and pg_hba.conf files after
making runtime configuration parameter changes but do not
shutdown the Greenplum Database array:
gpstop -u
*****************************************************
SEE ALSO
*****************************************************
gpstart
常用的参数如下：
-a，不需要输入Y确认是否关闭，将直接关闭数据库。
-m，只关闭Master节点。
-r，重启数据库。
-u，加载参数文件，使修改的参数生效。
-M，设置关闭数据库的级别，有三种级别，fast、immediate和smart，gpstop –M fast，所有连接将中断并且回滚。gpstop –M immediate，强制关闭数据库，这种方式是不一致的关闭模式，不建议使用。Immediate smart，这是默认的关闭级别，所有连接的会话会收到关闭警告，不允许新链接访问数据库。下面是默认级别关闭GreenPlum数据库的相关信息。
[gpadmin@mdw gpdb]$ gpstop -a 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Starting gpstop with args: -a 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Gathering information and validating the environment... 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Obtaining Segment details from master... 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Greenplum Version: 'postgres (Greenplum Database) 4.3.6.2 build 1' 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-There are 0 connections to the database 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Commencing Master instance shutdown with mode='smart' 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Master host=mdw 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Commencing Master instance shutdown with mode=smart 20160114:10:55:17:013853 gpstop:mdw:gpadmin-[INFO]:-Master segment instance directory=/gpdb/gpdata/master/gpseg-1 20160114:10:55:18:013853 gpstop:mdw:gpadmin-[INFO]:-Attempting forceful termination of any leftover master process 20160114:10:55:18:013853 gpstop:mdw:gpadmin-[INFO]:-Terminating processes for segment /gpdb/gpdata/master/gpseg-1 20160114:10:55:18:013853 gpstop:mdw:gpadmin-[INFO]:-No standby master host configured 20160114:10:55:18:013853 gpstop:mdw:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait... 20160114:10:55:18:013853 gpstop:mdw:gpadmin-[INFO]:-0.00% of jobs completed 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-100.00% of jobs completed 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:- Segments stopped successfully = 3 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:- Segments with errors during stop = 0 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:----------------------------------------------------- 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-Successfully shutdown 3 of 3 segment instances 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-Database successfully shutdown with no errors reported 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-Cleaning up leftover gpmmon process 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-No leftover gpmmon process found 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-Cleaning up leftover gpsmon processes 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-No leftover gpsmon processes on some hosts. not attempting forceful termination on these hosts 20160114:10:55:28:013853 gpstop:mdw:gpadmin-[INFO]:-Cleaning up leftover shared memory
GreenPlum数据库启动关闭及数据库状态检查：等您坐沙发呢！
发表评论
