Datasource Statuses

In addition to the overall state, all datasources have a specific status that indicates the current health and operation, rather than the configured state for that datasource. For example, a datasource can be in the online state, but have a DIMINISHED status if there is a recoverable problem with one of the datasource components.

The purpose of the STATUS field is to provide standard, datasource-state-specific values for ease of parsing and backwards-compatibility with older versions of the cctrl command.

The STATUS field is effectively the same information as the datasource state that appears on the first line after the colon (:), just presented slightly differently.

Here are the possible values for STATUS, showing the Datasource State first, and the matching STATUS second:

Role	Supplies Replication Data	Receives Replication Data	Load Balancing	Failover
master	Yes	No	Yes	Yes
slave	No	Yes	Yes	Yes
relay	Yes	Yes	Yes	Yes
standby	No	Yes	No	Yes
archive	No	Yes	Yes	No

Any other datasource status sets the STATUS to UNKNOWN.

• OK

  The OK status indicates that the datasource is currently operating correctly.

• DIMINISHED

  A DIMINISHED status indicates that there is a problem with one of the dataservice services which is causing a reduced level of expected service. For example, in the sample output below, the reason is indicated as a stopped replicator service.

  +----------------------------------------------------------------------------+
  |db1(master:ONLINE)                                                          |
  |STATUS [DIMINISHED] [2025/01/24 03:23:02 PM UTC]                            |
  |REASON[REPLICATOR STOPPED]                                                  |
  +----------------------------------------------------------------------------+
  |  MANAGER(state=ONLINE)                                                     |
  |  REPLICATOR(state=STOPPED)                                                 |
  |  DATASERVER(state=ONLINE)                                                  |
  |  CONNECTIONS(created=195, active=0)                                        |
  +----------------------------------------------------------------------------+

  The underlying service fault should be fixed and the status rechecked.

If all the services are ONLINE, but one node is in the DIMINISHED state, you should let the auto-recovery process complete. To do this:

1. Place the cluster into AUTOMATIC mode:

   [LOGICAL] /alpha > set policy automatic

2. Set the status of the node in the DIMINISHED state to OFFLINE:

   [object Object]

Automatic recovery will then recover the node for you.

Datasource States and Policy Mode Interactions

States can be explicitly set through cctrl, however, depending on the current policy mode, the actual status set may be different from that initially set. For example, when shunning a datasource, the datasource will immediately go into SHUNNED state.

[LOGICAL] /alpha > datasource db2 shun
DataSource 'db2' set to SHUNNED

To bring the datasource back into operation, it must be brought back using the recover command:

[LOGICAL] /alpha > datasource db2 recover
DataSource 'db2' is now OFFLINE

The datasource recover command performs whatever steps are necessary to bring the datasource back into operation within the dataservice. Even for manually shunned datasources, there may be additional configuration or recovery steps required.

If the dataservice policy mode is MANUAL or MAINTENANCE modes, the datasource remains in the OFFLINE state until manually put ONLINE.