Rollover API errors out with NPE in some cases #43296
Assignees
Labels
Comments
dakrone
added
:Data Management/Indices APIs
|
Pinging @elastic/es-core-features |
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Jun 18, 2019
It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves elastic#43296
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Jun 19, 2019
It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves elastic#43296
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Jun 19, 2019
It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves elastic#43296
dakrone
added a commit
that referenced
this issue
Jun 19, 2019
It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves #43296
dakrone
added a commit
that referenced
this issue
Jun 19, 2019
#43397) It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves #43296
dakrone
added a commit
that referenced
this issue
Jun 19, 2019
#43398) It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves #43296
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Aug 23, 2019
It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves elastic#43296
dakrone
added a commit
that referenced
this issue
Aug 23, 2019
) It's possible for the passed in `IndexMetaData` to be null (for instance, cluster state passed in does not have the index in its metadata) which in turn can cause a `NullPointerException` when evaluating the conditions for an index. This commit adds null protection and unit tests for this case. Resolves #43296
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Elasticsearch version (
bin/elasticsearch --version): 7.0.1Plugins installed: []
JVM version (
java -version): OpenJDK 12.0.1OS version (
uname -aif on a Unix-like system): UnknownDescription of the problem including expected versus actual behavior:
ILM job to create rollover indices when the index hits 500GB
Steps to reproduce:
ILM calls rollover API
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: