Starting , Stopping, restarting Greenplum Chorus

Starting and Stopping Greenplum Chorus 2.4

1. Log in as user, chorus. 

Important: You should not perform these tasks as root.

2. Run the commands to perform each of the following tasks.

To start Greenplum Chorus 

$ cd <chorus install path>

$ source chorus_path.sh

$ chorus_control.sh start

==========================================================================================

[chorus@sachi greenplum-chorus]$ source chorus_path.sh

[chorus@sachi greenplum-chorus]$ chorus_control.sh start

Setting maximum database connections to 100

[production] postgres started as pid 5683

[production] Worker started as pid 5778

[production] Scheduler started as pid 5861

[production] Solr started as pid 5958 on port 8983

[production] Writing nginx config...

[production] nginx started as pid 6135

[production] updating jetty config...

[production] starting jetty...

[chorus@sachi greenplum-chorus]$ 

==========================================================================================

To stop Greenplum Chorus

$ cd <chorus install path>

$ source chorus_path.sh

$ chorus_control.sh stop

To restart Greenplum Chorus

$ cd <chorus install path>

$ source chorus_path.sh

$ chorus_control.sh restart

==========================================================================================

[chorus@sachi ~]$ pwd

/home/chorus

[chorus@sachi ~]$ cd /usr/local/greenplum-chorus/

[chorus@sachi greenplum-chorus]$ ls

chorus_control.sh  chorus_path.sh  chorus_psql.sh  chorus_rails_console.sh  current  install.log  releases  shared

[chorus@sachi greenplum-chorus]$ source chorus_path.sh

[chorus@sachi greenplum-chorus]$ chorus_control.sh restart

[production] stopping nginx  ( Stopped )

[production] stopping jetty Stopping Jetty: OK

 ( Stopped )

[production] stopping solr  ( Stopped )

[production] stopping scheduler  ( Stopped )

[production] stopping workers . ( Stopped )

[production] stopping postgres  ( Stopped )

Setting maximum database connections to 100

[production] postgres started as pid 26449

[production] Worker started as pid 26656

[production] Scheduler started as pid 26757

[production] Solr started as pid 26841 on port 8983

[production] Writing nginx config...

[production] nginx started as pid 26998

[production] updating jetty config...

[production] starting jetty...

[chorus@sachi greenplum-chorus]$ 

==========================================================================================

To monitor Greenplum Chorus

Monitoring consists of checking that all chorus processes are running and restarting any processes that are down.

$ cd <chorus install path>

$ source chorus_path.sh

$ chorus_control.sh monitor

To backup Chorus data

$ cd <chorus install path>

$ source chorus_path.sh

$ chorus_control.sh backup [-d dir] [-r days]

where -d supplies the directory for the backup and -r specifies how many days of backup files should be kept in the backup directory. Files more than r days old will 

be removed.