Deduplicating the compactor docs (#4345)

* deduplicating the compactor docs :D same list crept in twice! * Update wording. Co-authored-by: Karen Miller <[email protected]> Co-authored-by: Karen Miller <[email protected]>
grafana · Sep 20, 2021 · a140bc7 · a140bc7
1 parent eef896c
commit a140bc7
Showing 1 changed file with 2 additions and 8 deletions.
diff --git a/docs/sources/operations/storage/retention.md b/docs/sources/operations/storage/retention.md
@@ -33,13 +33,7 @@ The retention algorithm is applied to the index. Chunks are not deleted while ap
 
 Marked chunks will only  be deleted after `retention_delete_delay` configured is expired because:
 
-1. boltdb-shipper indexes are refreshed from the shared store on components using it (querier and ruler) at a specific interval. This means deleting chunks instantly could lead to components still having reference to old chunks and so they could fails to execute queries. Having a delay allows for components to refresh their store and so remove gracefully their reference of those chunks.
-
-2. It gives you a short period to cancel chunks deletion in case of mistakes.
-
-Marked chunks will only  be deleted after `retention_delete_delay` configured is expired because
-
-- boltdb-shipper indexes are refreshed from the shared store on components using them (querier and ruler) at a specific interval. Deleting chunks instantly could lead to components still having a reference to old chunks. This could, in turn, cause query execution failure. Having a delay allows components to refresh their store and gracefully remove their reference to those chunks.
+- boltdb-shipper indexes are refreshed from the shared store on components using it (querier and ruler) at a specific interval. This means deleting chunks instantly could lead to components still having reference to old chunks and so they could fails to execute queries. Having a delay allows for components to refresh their store and so remove gracefully their reference of those chunks.
 
 - It provides a short window of time in which to cancel chunk deletion in the case of a configuration mistake.
 
@@ -231,4 +225,4 @@ chunk_store_config:
 table_manager:
   retention_deletes_enabled: true
   retention_period: 672h
-```
+```