Troubleshooting the Cassandra database issues


This topic describes the issues that might commonly occur in the Cassandra database. 

I cannot continue with the CDP upgrade and the error message about Cassandra still running appears

Problem: While upgrading 

Some content is unavailable due to permissions.

CDP from version 8.0 to 8.0.01, if the Cassandra database is not stopped automatically, the following warning message appears on the installer:

DRAUM-23371.png

This issue may only occur on the Windows operating system. 

Reason: This issue occurs because a java process associated with the Working-with-the-Apache-Cassandra-database is still running even when the CDP service is stopped before the upgrade. Hence the installation program is not able to upgrade the Cassandra database and restore the backup. No explanatory error message appears on the installation screen and the upgrade fails. 

Solution: Before upgrading the CDP, ensure that the Cassandra database is stopped. 

Perform the following steps to stop the cassandra process

Before stopping the Cassandra database, you must ensure that the process ID in the pid.txt file for Cassandra matches the process ID for the java process running from the CDP installation directory.

  1. On the server where the CDP is running, go to the Task Manager and locate the java process.
  2. Copy the java process ID and then go to <AO_HOME>\BAO\CDP\cassandra and open the pid.txt file.
  3. If the process ID in the pid.txt file does not match the java process ID, change the process ID to match the java process ID.
  4. From the command prompt, run the following command to stop the Cassandra database:

    <AO_HOME/cassandra/bin>stop-server.bat -p ..\pid.txt -f

Jobs are running on the Grid but data is not displayed on the Job View or Job List on the Health Dashboard

If the data for the latest jobs running on the Grid is not reflecting on the Job View or Job List on the Health Dashboard, you may want to verify if Apache Cassandra node for the peer to which the dashboard is connected in running successfully. 

If the Cassandra node is down, restart it manually. This issue occurs mostly on Windows 2008 R2 server. 

To start the Cassandra node:

  1. Go to command prompt and run the following command:

    powershell Set-ExecutionPolicy Unrestricted
  2. Go to AO_HOME/cassandra/bin file.
  3. (Windows) Run the cassandra.bat file.
    (Linux) Run the cassandra file.
    Cassandra node is started.

If the job data is not displayed even after restarting the cassandra database, verify if the installation path as specified while installing the CDP contains any spaces. Run the following command to restart the cassandra database:

<AO_HOME/cassandra/bin> cassandra.bat legacy

Related topic

Known-and-corrected-issues

Working-with-the-Apache-Cassandra-database

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*