Table of Contents

Checking the node status


Only available versions of this content are shown in the dropdown

Check the status of Decision Data Store (DDS) nodes, for example, to troubleshoot Cassandra-related failures listed in Pega logs.

  1. In the header of Dev Studio, click Configure Decisioning Infrastructure Services Decision Data Store .

  2. On the Decision Data Store landing page, ensure that data correctly replicates across nodes by verifying that the ownership percentages of all DDS nodes add up to 100%.

    To check the ownership percentage for a selected node, click the status of the node, and then examine the Owns section.
  3. Check the node state in the nodetool utility:

    1. In the nodetool utility, run the nodetool status command.

      Nodetool returns a cluster status report, as in the following example:
      Datacenter: datacenter1
      |/ State=Normal/Leaving/Joining/Moving
      --  Address     Load       Tokens  Owns (effective)  Host ID                               Rack
      UN   229.36 KB  256     100.0%            69d1a4da-fe18-483f-9ff8-5ffa8af94eca  rack1
      UN   125.13 KB  256     100.0%            1fc331b1-47af-4760-973d-a34903fb0235  rack1
      UN  103.92 KB  256     100.0%            2ddffb1d-1bf1-4b20-9da9-a305f325826e  rack1
      The ownership percentages in the nodetool report are different than the percentages shown on the DDS landing page. The nodetool report describes both original data and replicated data, whereas the DDS landing page only refers to original data. For example, for a three-node cluster with a replication factor of 3, the nodetool report returns a 100% ownership for each node; for a four-node cluster with a replication factor of 3, the nodetool report returns a 75% ownership for each node, and so on.
    2. Ensure that the cluster status report lists all nodes.

    3. In the -- column, ensure that all nodes are marked as UN.

      UN means that the node status is UP and that the node state is NORMAL.
  4. If a node does not have UN status, investigate the source of the problem, for example, by performing other Cassandra troubleshooting procedures.

    For more information, see the Troubleshooting section of the Apache Cassandra documentation.

Related Content

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.