Stopping a Global Service

To stop a running GDS global service on pool databases, perform GDSCTL stop service (optionally -database).

A global service running on databases in a Global Data Services pool can be shut down by the stop service command. If the stop service command is executed with the -database option, then the service is stopped on the specified databases; otherwise it is stopped on all databases in the pool. For example:

GDSCTL>stop service -gdspool readerfarm -service sales_report

Note:

A stopped service with the automatic management policy is restarted if the database where it was running gets restarted and is eligible to run the service. Also, stopping a service with the automatic management policy on all databases in a Global Data Services pool does not prevent the automatic service startup on a new database when the service is created there. To completely disable the automatic startup of a service, its management policy should be changed to manual.

When the service is stopped by the user, the Global Data Services framework considers that database to be temporarily unavailable for this service. Stopping a global service does n ot cause a service failover event; the service cardinality is temporarily decreased and the global service manager does not attempt to start the service on another database in the pool.

However, a database with a stopped service is still considered a failover target for this service; when the service fails on another database, it can be started on this database if it is eligible to run the service. After the service failover to a database, the service on that database is no longer considered to be stopped by the user.

A stopped service can be manually restarted by executing the start service command.