Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Input/output blockages in the Cassandra cluster

Updated on April 5, 2022

This content applies only to On-premises and Client-managed cloud environments

Address input/output (I/O) blockages in a Cassandra cluster or low CPU resources by reviewing the CPU statistics.

  1. From a Linux terminal, run the top command.Result: The Linux terminal returns a report on system resource usage and current processes.
  2. In the Linux report, find the CPU usage section (%Cpu(s)).Result: The CPU usage section shows the percentage of CPU time spent on various tasks, for example:
    %Cpu(s): 12.8 us, 2.3 sy, 0.0 ni, 84.4 id, 0.3 wa, 0.0 hi, 0.2 si, 0.0 st

    The value of the wa parameter reflects the time that the CPU spends waiting for I/O operations to complete.

  3. If the value of the wa parameter is higher than 1, 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.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us