dump cldbstate

Prints the state of the container location database (CLDB).

Syntax

CLI
maprcli dump cldbstate
     [ -cluster cluster_name ]
     [ -hostip host name or ip ]
REST
N/A

Parameters

Parameter

Description

cluster The cluster on which to run the command. If this parameter is omitted, the command is run on the same cluster where it is issued. In multi-cluster contexts, you can use this parameter to specify a different cluster on which to run the command.
hostip The node from which to retrieve the state of CLDB. If this parameter is omitted, the command returns the CLDB state from all nodes in the cluster.

Output

The maprcli dump cldbstate command lists the state of the CLDB database.

$ maprcli dump cldbstate
mode               ip           state                    stateDuration  desc
SLAVE_READ_ONLY    x.x.x.x CLDB_IS_SLAVE_READ_ONLY    03:54:25      cldb running as slave
SLAVE_READ_ONLY    x.x.x.x CLDB_IS_SLAVE_READ_ONLY    03:54:16      cldb running as slave
MASTER_READ_WRITE  x.x.x.x CLDB_IS_MASTER_READ_WRITE  04:07:58      kvstore tables loading complete, 
                                                                     cldb running as master

Output Fields

Field Description
mode The CLDB mode. A CLDB instance can either run as a Primary or a Secondary instance. The only two states that a CLDB instance should settle in are:
  • SLAVE_READ_ONLY
  • MASTER_READ_WRITE

If a CLDB instance spends a significant amount of time in a state other than these two, then it is highly likely that there is an issue that requires administrative intervention.

ip The IP address of the node from which the CLDB state is retrieved.
state Indicates whether the CLDB instance is run as a Secondary with READ_ONLY privilege, or as a Primary with READ_WRITE privilege.
stateDuration The amount of time in HH:MM:SS format that the CLDB instance has spent in this state.
desc The description of the state (either Primary or Secondary).