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.

Verifying the keyspace replication factor

Updated on April 5, 2022

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

Troubleshoot keyspace-related errors, such as incorrect replication, by checking whether a specific keyspace exists and whether the keyspace belongs to the correct data center.

  • View the keyspace details by entering describe keyspace keyspace_name in the cqlsh console.
    Cassandra returns output similar to the following:
    
    CREATE KEYSPACE data WITH replication = {'class': 'NetworkTopologyStrategy', 'datacenter1': '3'} AND durable_writes = true;
    
    where:
    • class is the replication strategy.
    • datacenter1 is the name of the related data center. The data center name is associated with the current replication factor value, for example, 3.
What to do next: Depending on the output, you might want to adjust the keyspace configuration to better reflect your business needs and prevent replication errors. For example, you can use the alter_keyspace command to fix the keyspace configuration. For more information, see 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