summaryrefslogtreecommitdiffstats
path: root/health/guides/riakkv/riakkv_list_keys_active.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-03-09 13:19:48 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-03-09 13:20:02 +0000
commit58daab21cd043e1dc37024a7f99b396788372918 (patch)
tree96771e43bb69f7c1c2b0b4f7374cb74d7866d0cb /health/guides/riakkv/riakkv_list_keys_active.md
parentReleasing debian version 1.43.2-1. (diff)
downloadnetdata-58daab21cd043e1dc37024a7f99b396788372918.tar.xz
netdata-58daab21cd043e1dc37024a7f99b396788372918.zip
Merging upstream version 1.44.3.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'health/guides/riakkv/riakkv_list_keys_active.md')
-rw-r--r--health/guides/riakkv/riakkv_list_keys_active.md31
1 files changed, 31 insertions, 0 deletions
diff --git a/health/guides/riakkv/riakkv_list_keys_active.md b/health/guides/riakkv/riakkv_list_keys_active.md
new file mode 100644
index 000000000..38d42a37e
--- /dev/null
+++ b/health/guides/riakkv/riakkv_list_keys_active.md
@@ -0,0 +1,31 @@
+### Understand the alert
+
+This alert indicates that currently there are active `list keys` operations in Finite State Machines (FSM) on your Riak KV database. Running `list keys` in Riak is a resource-intensive operation and can significantly affect the performance of the cluster, and it is not recommended for production use.
+
+### What are list keys operations in Riak?
+
+`List keys` operations in Riak involve iterating through all keys in a bucket to return a list of keys. The reason this is expensive in terms of resources is that Riak needs to traverse the entire dataset to generate a list of keys. As the dataset grows, the operation consumes more resources and takes longer to process the list, which can lead to reduced performance and scalability.
+
+### Troubleshoot the alert
+
+To address the `riakkv_list_keys_active` alert, follow these steps:
+
+1. Identify the processes and applications running `list keys` operations:
+
+ Monitor your application logs and identify the processes or applications that are using these operations. You may need to enable additional logging to capture information related to `list keys`.
+
+2. Evaluate the necessity of `list keys` operations:
+
+ Work with your development team and determine if there's a specific reason these operations are being used. If they are not necessary, consider replacing them with other, more efficient data retrieval techniques.
+
+3. Optimize data retrieval:
+
+ If it is necessary to retrieve keys in your application, consider using an alternative strategy such as Secondary Indexes (2i) or implementing a custom solution tailored to your specific use case.
+
+4. Monitor the system:
+
+ After making changes to your application, continue monitoring the active list key FSMs using Netdata to ensure that the number of active list keys operations is reduced.
+
+### Useful resources
+
+1. [Riak KV Operations](https://docs.riak.com/riak/kv/latest/developing/usage/operations/index.html)