Skip to content

More read-only-allow-delete docs #45320

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

DaveCTurner
Copy link
Contributor

Adds to the index.blocks.read_only_allow_delete docs the information that
this block may be added or removed automatically, and rewords the
breaking-changes docs to mention the blocks explicitly and to recommend using a
different block.

Relates #42559

Adds to the `index.blocks.read_only_allow_delete` docs the information that
this block may be added or removed automatically, and rewords the
breaking-changes docs to mention the blocks explicitly and to recommend using a
different block.

Relates elastic#42559
@DaveCTurner DaveCTurner added >docs General docs changes :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) v8.0.0 v7.4.0 labels Aug 8, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs

Copy link
Member

@original-brownbear original-brownbear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

some distance below the flood-stage watermark and therefore the disk space
problem is truly resolved. Since this block may be automatically removed, you
can no longer rely on adding this block manually to prevent writes to an index.
You should use the `index.blocks.read_only` block instead. This behaviour can
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: I know it was there before but behaviour -> behavior because we tend to do it the 🇺🇸 way in docs? (I'm sorry)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$ git annotate docs/reference/migration/migrate_7_4.asciidoc | grep behav
d73e2f9c5601	(Armin Braun	2019-07-15 10:21:54 +0200	68)If your application requires handling `+` as a single space you can return to the old behaviour by setting the system property
d73e2f9c5601	(Armin Braun	2019-07-15 10:21:54 +0200	69)`es.rest.url_plus_as_space` to `true`. Note that this behaviour is deprecated and setting this system property to `true` will cease
b47f74818634	(David Turner	2019-08-08 08:48:36 +0100	113)You should use the `index.blocks.read_only` block instead. This behaviour can

:trollface:

@DaveCTurner DaveCTurner merged commit ddcc38c into elastic:7.x Aug 8, 2019
@DaveCTurner DaveCTurner deleted the 2019-08-08-more-read_only_allow_delete-docs branch August 8, 2019 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >docs General docs changes v7.4.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants