Common Reference

The replicator Command

The replicator command is the wrapper script that handles the execution of the replicator service.

Usage

replicator [command] [options]

Option	Description	Version
`condrestart`	Restart only if already running.
`console`	Launch in the current console (instead of a daemon)
`dump`	Request a Java thread dump (if replicator is running)
`install`	Install the service to automatically start when the system boots.
`remove`	Remove the service from starting during boot.
`restart`	Stop replicator if already running and then start
`start`	Start in the background as a daemon process.
`status`	Query the current status.
`stop`	Stop if running (whether as a daemon or in another console)

Where:

`condrestart`

Restart the replicator, only if it is already running. This can be useful to use when changing configuration or performing database management within automated scripts, as the replicator will be only be restarted if it was previously running.

For example, if the replicator is running, replicator condrestart operates asreplicator restart:

shell> replicator condrestart
Stopping Tungsten Replicator Service...
Waiting for Tungsten Replicator Service to exit...
Stopped Tungsten Replicator Service.
Starting Tungsten Replicator Service...
Waiting for Tungsten  Replicator Service......
running: PID:26646

However, if not already running, the operation does nothing:

shell> replicator condrestart</userinput>
Stopping Tungsten Replicator Service...
Tungsten Replicator Service was not running.

Options for condrestart

Option	Description
`offline`	Start in OFFLINE state.

`offline`

Start in OFFLINE state.

`console`

Launch in the current console (instead of a daemon)

Options for console

Option	Description
`offline`	Start in OFFLINE state

`offline`

Start in OFFLINE state

`dump`

Request a Java thread dump (if replicator is running)

`install`

Installs the startup scripts for running the replicator at boot. For an alternative method of deploying these start-up scripts, see deployall.

`remove`

Removes the startup scripts for running the replicator at boot. For an alternative method of removing these start-up scripts, see undeployall.

`restart`

Warning

Restarting a running replicator temporarily stops and restarts replication.

Stops the replicator, if it is already running, and then restarts it:

shell> replicator restart
Stopping Tungsten Replicator Service...
Stopped Tungsten Replicator Service.
Starting Tungsten Replicator Service...
Waiting for Tungsten Replicator Service......
running: PID:26248

Options for restart

Option	Description
`offline`	Stop and restart in OFFLINE state.

`offline`

Stops the replicator, and starts it again in the OFFLINE state:

shell> replicator restart offline
Stopping Tungsten Replicator Service...
Stopped Tungsten Replicator Service.
Starting Tungsten Replicator Service...
Waiting for Tungsten Replicator Service......
running: PID:26435

`start`

To start the replicator service if it is not already running:

shell> replicator start
Starting Tungsten Replicator Service...

Options for start

Option	Description
`offline`	Start in OFFLINE state.

`offline`

Starts the replicator, but places the replicator into the OFFLINE state. This prevents the replicator from starting to process content, and may be used during provisioning operations.

shell> replicator start offline
Starting Tungsten Replicator Service...
Waiting for Tungsten Replicator Service......
running: PID:25760

`status`

Checks the execution status of the replicator:

shell> replicator statusp
Tungsten Replicator Service is running: PID:27015, Wrapper:STARTED, Java:STARTED

If the replicator is not running:

shell> replicator statusp>
Tungsten Replicator Service is not running.

This only provides the execution state of the replicator, not the actual state of replication. To get detailed information on the status of replication use trepctl reset.

`stop`

Stops the replicator if it is already running:

shell> replicator stop
Stopping Tungsten Replicator Service...
Waiting for Tungsten Replicator Service to exit...
Stopped Tungsten Replicator Service.

For Clustering Users

If the cluster was configured with auto-enable=false then you will need to put each node online manually using trepctl online