natas_hw
/
cassandra
mirror of https://github.com/apache/cassandra
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

CASSANDRA-21342: Long-tail xref follow-up (cassandra-4.0 subset) 

Subset of the trunk long-tail xref follow-up (commit cc97ee5332)
applicable to cassandra-4.0. Three files have broken patterns that
still apply on this branch after PR #4807's forward-merge: the
architecture index, finding_nodes, and use_tools self-page xrefs.

Six edits total. Mechanical retargets only; no prose was rewritten.

Edits omitted (trunk-only):
* Twenty files introduced in 5.0 or later (developing/cql/, reference/
  cql-commands/, managing/operating/, etc).
* use_tools.adoc edits 4 and 5 (different line state on 4.x;
  packet-capture anchor section structure differs).

 patch by Patrick McFadin; reviewed by Mick Semb Wever for CASSANDRA-21342
This commit is contained in:
Patrick McFadin 2026-06-10 10:59:01 -07:00
parent 8aa71cea52
commit 19ee803038
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/modules/cassandra/pages/architecture/index.adoc
View File

@ -6,4 +6,4 @@ This section describes the general architecture of Apache Cassandra.
* xref:architecture/dynamo.adoc[Dynamo]
* xref:architecture/storage_engine.adoc[Storage Engine]
* xref:architecture/guarantees.adoc[Guarantees]
* xref:architecture/snitch.adoc[Snitches]
* xref:cassandra:managing/operating/snitch.adoc[Snitches]

4
doc/modules/cassandra/pages/troubleshooting/finding_nodes.adoc
View File

@ -128,6 +128,6 @@ exhaust significant CPU capacitity with a "single" query.
Once you have narrowed down the problem as much as possible (datacenter,
rack , node), login to one of the nodes using SSH and proceed to debug
using xref:reading_logs.adoc[`logs`], xref:use_nodetooladoc[`nodetool`], and
xref:use_tools.adoc[`os tools`].
using xref:cassandra:troubleshooting/reading_logs.adoc[`logs`], xref:cassandra:troubleshooting/use_nodetool.adoc[`nodetool`], and
xref:cassandra:troubleshooting/use_tools.adoc[`os tools`].
If you are not able to login you may still have access to `logs` and `nodetool` remotely.

6
doc/modules/cassandra/pages/troubleshooting/use_tools.adoc
View File

@ -208,7 +208,7 @@ when it syncs the commit log. This typically enters into the very high
percentiles of write latency.
Note that to get detailed latency breakdowns you will need a more
advanced tool such as xref:use_tools.adoc#bcc-tools[`bcc-tools`].
advanced tool such as xref:cassandra:troubleshooting/use_tools.adoc#use-bcc-tools[`bcc-tools`].
=== OS page Cache Usage
@ -232,8 +232,8 @@ Cassandra performance can suffer significantly. This is why Cassandra
starts with a reasonably small amount of memory reserved for the heap.
If you suspect that you are missing the OS page cache frequently you can
use advanced tools like xref:use_tools.adoc#use-bcc-tools[cachestat] or
xref:use_tools.adoc#use-vmtouch[vmtouch] to dive deeper.
use advanced tools like xref:cassandra:troubleshooting/use_tools.adoc#use-bcc-tools[cachestat] or
xref:cassandra:troubleshooting/use_tools.adoc#use-vmtouch[vmtouch] to dive deeper.
=== Network Latency and Reliability