This could be a symptom for a flapping link.Ĭheck network latency and throughput between nodes, and between client and cluster. You may need to tune the TCP parameters of the Linux kernel, as described in Check OS Messages.Ĭarrier (only for TX) - number of packets that have experienced loss of carriers. Overruns - number of received packets that experienced FIFO overruns, which is caused by the rate at which a buffer gets full and the kernel is unable to empty. This could indicate symptoms for malfunctioning network hardware, either server or elsewhere in the network. Most system-level recommendations are applicable to both DSE and Cassandra.Įrrors - total number of packets received with errors (CRC, overruns, and so on). The DSE Troubleshooting guide includes a section on troubleshooting Linux-related issues and DataStax Support contains a knowledge base that should be checked for troubleshooting information. DataStax documentation includes chapters on recommended production settings (DSE 6.8 | 6.7 | 6.0 | 5.1). This document recommends a number of the system-level checks to execute when troubleshooting or planning a new setup of Cassandra or DSE clusters. ![]() This document does not cover troubleshooting of specific problems. The numbers may need to be adjusted depending on your requirements.Īpplying all the recommendations does not offer a strict guarantee on the cluster health breaking a rule is not necessarily an issue for a specific use case. The numbers provided here are not hard limits, but general recommendations to remain in a comfortable/safe zone. This document does not replace the official documentation.Įach use case can be different. This document requires either basic DSE or Cassandra knowledge, or both. This document gives a general recommendation for DataStax Enterprise (DSE) and Apache Cassandra™.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |