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

Jump to bottom

Can't set action.auto_create_index to any value(too restrictive) #33369

Closed
teuneboon opened this issue Sep 4, 2018 · 4 comments
Closed

Can't set action.auto_create_index to any value(too restrictive) #33369

teuneboon opened this issue Sep 4, 2018 · 4 comments
Labels
>bug :Data Management/Watcher v6.4.0

Comments

@teuneboon
Copy link

Elasticsearch version: 6.4.0

Plugins installed: []

JVM version: OpenJDK 1.8.0_181

OS version: Linux 3.16.0-5-amd64 #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64 GNU/Linux

Description of the problem including expected versus actual behavior:
When I try to set action.auto_create_index: false I get the following error when starting Elasticsearch:

Caused by: java.lang.IllegalArgumentException: the [action.auto_create_index] setting value [false] is too restrictive. disable [action.auto_create_index] or set it to [.watches, .triggered_watches, .watcher-history-*]

After trying some different values(-* and +foobar,-*) I decided to try setting it to exactly what the error message recommended: action.auto_create_index: watches, .triggered_watches, .watcher-history-* which is when I got the amazing error:

Caused by: java.lang.IllegalArgumentException: the [action.auto_create_index] setting value [.watches, .triggered_watches, .watcher-history-*] is too restrictive. disable [action.auto_create_index] or set it to [.watches, .triggered_watches, .watcher-history-*]

The initial issue still isn't solved(still can't disable automatic index creation), but this seems like a documentation/errormessage bug at the very least.

Steps to reproduce:

  1. Install Elasticsearch 6.4.0
  2. Put action.auto_create_index: false in elasticsearch.yml
  3. (Re)start Elasticsearch
@colings86 colings86 added the :Core/Infra/Core Core issues without another label label Sep 4, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@danielmitterdorfer
Copy link
Member

Thanks for raising the issue.

You need to specify the index patterns without any spaces in between. The following works:

action.auto_create_index: ".watches,.triggered_watches,.watcher-history-*"

(note how I removed the spaces after each comma).

I'll create a PR to remove the spaces in the error message so it is copy&pasteable.

danielmitterdorfer added a commit to danielmitterdorfer/elasticsearch that referenced this issue Sep 7, 2018
@danielmitterdorfer
Make Watcher validation message copy/pasteable
99470f0 
Watcher validates `action.auto_create_index` upon startup. If a user
specifies a pattern that does not contain watcher indices, it raises an
error message to include a list of three indices. However, the indices
are separated by a comma and a space which is not considered in parsing.

With this commit we change the error message string so it does not
contain the additional space thus making it more straightforward to copy
it to the configuration file.

Closes elastic#33369
@danielmitterdorfer danielmitterdorfer mentioned this issue Sep 7, 2018
Merged
@danielmitterdorfer danielmitterdorfer added :Data Management/Watcher and removed :Core/Infra/Core Core issues without another label labels Sep 7, 2018
@teuneboon
Copy link
Author

Alright thanks, this fixes it.

danielmitterdorfer added a commit that referenced this issue Sep 7, 2018
@danielmitterdorfer
Make Watcher validation message copy/pasteable
90c99ea 
Watcher validates `action.auto_create_index` upon startup. If a user
specifies a pattern that does not contain watcher indices, it raises an
error message to include a list of three indices. However, the indices
are separated by a comma and a space which is not considered in parsing.

With this commit we change the error message string so it does not
contain the additional space thus making it more straightforward to copy
it to the configuration file.

Closes #33369
Relates #33497
danielmitterdorfer added a commit that referenced this issue Sep 7, 2018
@danielmitterdorfer
Make Watcher validation message copy/pasteable
53f4f2f 
Watcher validates `action.auto_create_index` upon startup. If a user
specifies a pattern that does not contain watcher indices, it raises an
error message to include a list of three indices. However, the indices
are separated by a comma and a space which is not considered in parsing.

With this commit we change the error message string so it does not
contain the additional space thus making it more straightforward to copy
it to the configuration file.

Closes #33369
Relates #33497
@alexcojocaru alexcojocaru mentioned this issue Jul 1, 2019
Closed
@cavalier23
Copy link

cavalier23 commented Oct 13, 2020 •
edited

Thanks for raising the issue.

You need to specify the index patterns without any spaces in between. The following works:

action.auto_create_index: ".watches,.triggered_watches,.watcher-history-*"

(note how I removed the spaces after each comma).

I'll create a PR to remove the spaces in the error message so it is copy&pasteable.

that means we can't close action.auto_create_index setting? btw, I just tried this on elasticsearch server version of 7.9.2, still can't close auto_create_index! @danielmitterdorfer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug :Data Management/Watcher v6.4.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@colings86 @teuneboon @danielmitterdorfer @elasticmachine @cavalier23