Skip to content
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

Remove auto_release_flood_stage_block property check #114696

Merged
merged 2 commits into from
Oct 24, 2024

Conversation

arteam
Copy link
Contributor

@arteam arteam commented Oct 14, 2024

There's no option to disable the auto release of the write block when a node exceeds the flood-stage watermark.

This property was deprecated in #45274 (8.0)

@arteam arteam added :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >non-issue labels Oct 14, 2024
@arteam arteam marked this pull request as ready for review October 16, 2024 08:06
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@elasticsearchmachine elasticsearchmachine added the Team:Distributed Meta label for distributed team (obsolete) label Oct 16, 2024
@ldematte ldematte removed their request for review October 16, 2024 08:27
Copy link
Contributor

@nicktindall nicktindall left a comment

Choose a reason for hiding this comment

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

LGTM

@arteam arteam merged commit a281d62 into elastic:main Oct 24, 2024
16 checks passed
davidkyle pushed a commit to davidkyle/elasticsearch that referenced this pull request Oct 24, 2024
There's no option to disable the auto release of the write block when a node exceeds the flood-stage watermark.

This property was deprecated in elastic#45274 (8.0)
georgewallace pushed a commit to georgewallace/elasticsearch that referenced this pull request Oct 25, 2024
There's no option to disable the auto release of the write block when a node exceeds the flood-stage watermark.

This property was deprecated in elastic#45274 (8.0)
jfreden pushed a commit to jfreden/elasticsearch that referenced this pull request Nov 4, 2024
There's no option to disable the auto release of the write block when a node exceeds the flood-stage watermark.

This property was deprecated in elastic#45274 (8.0)
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) >non-issue Team:Distributed Meta label for distributed team (obsolete) v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants