You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Forbid read-only-allow-delete block in blocks API (#58727)
* Forbid read-only-allow-delete block in blocks API
The read-only-allow-delete block is not really under the user's control
since Elasticsearch adds/removes it automatically. This commit removes
support for it from the new API for adding blocks to indices that was
introduced in #58094.
* Missing xref
* Reword paragraph on read-only-allow-delete block
Copy file name to clipboardExpand all lines: docs/reference/index-modules/blocks.asciidoc
+20-15Lines changed: 20 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -22,16 +22,6 @@ index:
22
22
Set to `true` to make the index and index metadata read only, `false` to
23
23
allow writes and metadata changes.
24
24
25
-
`index.blocks.read_only_allow_delete`::
26
-
27
-
Similar to `index.blocks.read_only`, but also allows deleting the index to
28
-
make more resources available. The <<disk-based-shard-allocation,disk-based shard
29
-
allocator>> may add and remove this block automatically.
30
-
31
-
Deleting documents from an index to release resources - rather than deleting the index itself - can increase the index size over time. When `index.blocks.read_only_allow_delete` is set to `true`, deleting documents is not permitted. However, deleting the index itself releases the read-only index block and makes resources available almost immediately.
32
-
33
-
IMPORTANT: {es} adds and removes the read-only index block automatically when the disk utilization falls below the high watermark, controlled by <<cluster-routing-flood_stage,cluster.routing.allocation.disk.watermark.flood_stage>>.
34
-
35
25
`index.blocks.read`::
36
26
37
27
Set to `true` to disable read operations against the index.
@@ -46,6 +36,26 @@ IMPORTANT: {es} adds and removes the read-only index block automatically when th
46
36
47
37
Set to `true` to disable index metadata reads and writes.
48
38
39
+
`index.blocks.read_only_allow_delete`::
40
+
41
+
Similar to `index.blocks.read_only`, but also allows deleting the index to
42
+
make more resources available. The <<disk-based-shard-allocation,disk-based shard
43
+
allocator>> adds and removes this block automatically.
44
+
45
+
Deleting documents from an index - rather than deleting the index itself - can
46
+
in fact increase the index size. When you are running out of disk space
47
+
`index.blocks.read_only_allow_delete` is set to `true`, preventing you from
48
+
consuming more disk space by deleting some documents. However, this block does
49
+
permit you to delete the index itself since this does not require any extra
50
+
disk space. When you delete an index the data is removed from disk almost
51
+
immediately, freeing the space it consumes.
52
+
53
+
IMPORTANT: {es} adds the read-only-allow-delete index block automatically when
54
+
disk utilisation exceeds the <<cluster-routing-flood_stage,flood-stage
55
+
watermark>> and removes it again when disk utilisation is below the
56
+
<<cluster-routing-watermark-high,high watermark>>. You should not apply this
57
+
block yourself.
58
+
49
59
[discrete]
50
60
[[add-index-block]]
51
61
=== Add index block API
@@ -94,11 +104,6 @@ Disable read operations.
94
104
`read_only`::
95
105
Disable write operations and metadata changes.
96
106
97
-
`read_only_allow_delete`::
98
-
Disable write operations and metadata changes.
99
-
Document deletion is disabled.
100
-
However, index deletion is still allowed.
101
-
102
107
`write`::
103
108
Disable write operations. However, metadata changes are still allowed.
0 commit comments