-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Updating unchanged ILM policies is not idempotent. #82065
Labels
>bug
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
Team:Data Management
Meta label for data/management team
Comments
DaveCTurner
added
the
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
label
Dec 23, 2021
elasticmachine
added
the
Team:Data Management
Meta label for data/management team
label
Dec 23, 2021
Pinging @elastic/es-data-management (Team:Data Management) |
DaveCTurner
added
Team:Data Management
Meta label for data/management team
and removed
Team:Data Management
Meta label for data/management team
needs:triage
Requires assignment of a team area label
labels
Dec 23, 2021
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Jan 5, 2022
This commit makes `PUT`-ing an ILM policy that does not change a no-op, neither incrementing the version nor creating a new cluster state. Resolves elastic#82065
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 5, 2022
This commit makes `PUT`-ing an ILM policy that does not change a no-op, neither incrementing the version nor creating a new cluster state. Resolves #82065
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Jan 5, 2022
This commit makes `PUT`-ing an ILM policy that does not change a no-op, neither incrementing the version nor creating a new cluster state. Resolves elastic#82065
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 6, 2022
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this issue
Jan 7, 2022
This commit makes `PUT`-ing an ILM policy that does not change a no-op, neither incrementing the version nor creating a new cluster state. Resolves elastic#82065
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this issue
Jan 7, 2022
This commit makes `PUT`-ing an ILM policy that does not change a no-op, neither incrementing the version nor creating a new cluster state. Resolves elastic#82065
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
Team:Data Management
Meta label for data/management team
Elasticsearch version (
bin/elasticsearch --version
): docker.elastic.co/elasticsearch/elasticsearch:7.16.2-amd64Plugins installed: Whatever the docker container ships
JVM version (
java -version
): Whatever the docker container shipsOS version (
uname -a
if on a Unix-like system): Whatever the docker container shipsDescription of the problem including expected versus actual behavior:
Updating an ILM policy always increases the version of the stored policy. @DaveCTurner suggested to open an issue here. I did not check if other operations (updating index templates and mappings) are idempotent or not.
Steps to reproduce:
docker run --rm -it -p 9200:9200 -e "discovery.type=single-node" -e "logger.org.elasticsearch=DEBUG" docker.elastic.co/elasticsearch/elasticsearch:7.16.2-amd64
multiple times
3. Check the ILM version:
curl http://localhost:9200/_ilm/policy/my_policy
4. The returned version is greater than 1 even though nothing changed
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: