Skip to content

Conversation

@jakelandis
Copy link
Contributor

This commit adds support to check for negative values for index setting
index.unassigned.node_left.delayed_timeout for the deprecation info API.

relates #36024
relates #26828

…eout

This commit adds support to check for negative values for index setting
`index.unassigned.node_left.delayed_timeout` for the deprecation info API.

relates elastic#36024
relates elastic#26828
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

Copy link
Contributor

@gwbrown gwbrown left a comment

Choose a reason for hiding this comment

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

Left one note about the details message, otherwise looks good. Thanks again!

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

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

I left a couple of nits but structurally this looks good. CI seems to be all kinds of broken here. Perhaps it needs to be merged with a known-good recent commit from master?

@jakelandis
Copy link
Contributor Author

@gwbrown @DaveCTurner thanks for the reviews. changes implemented. Below is the final output.

"index_settings" : {
    "test" : [
      {
        "level" : "warning",
        "message" : "Negative values for index.unassigned.node_left.delayed_timeout are deprecated and should be set to 0",
        "url" : "https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-7.0.html#_literal_index_unassigned_node_left_delayed_timeout_literal_may_no_longer_be_negative",
        "details" : "The index [test] has [index.unassigned.node_left.delayed_timeout] set to [-1m], but negative values are not allowed"
      }
    ]
  }

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

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

LGTM

@jakelandis jakelandis merged commit 52fee63 into elastic:6.x Dec 13, 2018
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Nov 12, 2025
When file settings tests look for changes in cluster state to assert
application of changes they do so by adding a cluster state listener.
But if there are no more cluster state updates after the listener is
added the test will never see the initial state of file settings. This
commit ensures the current cluster state is seen in that case.

closes elastic#36454
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants