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

elasticsearch-shard can not parse an index that has been rolled over #44628

Closed
jasontedor opened this issue Jul 19, 2019 · 1 comment · Fixed by #45036
Closed

elasticsearch-shard can not parse an index that has been rolled over #44628

jasontedor opened this issue Jul 19, 2019 · 1 comment · Fixed by #45036
Assignees
Labels
>bug :Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one.

Comments

@jasontedor
Copy link
Member

This is because it is not loading named writeables and therefore can not parse the condition that led to the rollover:

Caused by: java.io.IOException: failed to read /home/jason/.rally/benchmarks/races/2019-07-19-06-20-40/rally-node-0/install/elasticsearch-8.0.0-SNAPSHOT/data/indices/DnVmdtIuTVuJPIt0rUblFA/_state/state-7.st
        at org.elasticsearch.gateway.MetaDataStateFormat.loadGeneration(MetaDataStateFormat.java:408)
        ... 10 more
Caused by: org.elasticsearch.common.xcontent.XContentParseException: [-1:1028] [rollover_info] failed to parse field [met_conditions]
        at org.elasticsearch.common.xcontent.ObjectParser.parseValue(ObjectParser.java:386)
        at org.elasticsearch.common.xcontent.ObjectParser.parseSub(ObjectParser.java:396)
        at org.elasticsearch.common.xcontent.ObjectParser.parse(ObjectParser.java:238)
        at org.elasticsearch.common.xcontent.ConstructingObjectParser.parse(ConstructingObjectParser.java:169)
        at org.elasticsearch.common.xcontent.ConstructingObjectParser.apply(ConstructingObjectParser.java:161)
        at org.elasticsearch.action.admin.indices.rollover.RolloverInfo.parse(RolloverInfo.java:72)
        at org.elasticsearch.cluster.metadata.IndexMetaData$Builder.fromXContent(IndexMetaData.java:1346)
        at org.elasticsearch.cluster.metadata.IndexMetaData$2.fromXContent(IndexMetaData.java:1462)
        at org.elasticsearch.cluster.metadata.IndexMetaData$2.fromXContent(IndexMetaData.java:1451)
        at org.elasticsearch.gateway.MetaDataStateFormat.read(MetaDataStateFormat.java:302)
        at org.elasticsearch.gateway.MetaDataStateFormat.loadGeneration(MetaDataStateFormat.java:404)
        ... 10 more
Caused by: org.elasticsearch.common.xcontent.XContentParseException: [-1:1028] [met_conditions] failed to parse field [max_docs]
        at org.elasticsearch.common.xcontent.ObjectParser.lambda$declareNamedObjects$6(ObjectParser.java:314)
        at org.elasticsearch.common.xcontent.ObjectParser.lambda$declareNamedObjects$7(ObjectParser.java:326)
        at org.elasticsearch.common.xcontent.ObjectParser.parseValue(ObjectParser.java:384)
        ... 20 more
Caused by: org.elasticsearch.common.xcontent.NamedObjectNotFoundException: unknown named object category [org.elasticsearch.action.admin.indices.rollover.Condition]
        at org.elasticsearch.common.xcontent.NamedXContentRegistry.parseNamedObject(NamedXContentRegistry.java:128)
        at org.elasticsearch.common.xcontent.support.AbstractXContentParser.namedObject(AbstractXContentParser.java:385)
        at org.elasticsearch.action.admin.indices.rollover.RolloverInfo.lambda$static$1(RolloverInfo.java:51)
        at org.elasticsearch.common.xcontent.ObjectParser.lambda$declareNamedObjects$6(ObjectParser.java:312)
        ... 22 more
@jasontedor jasontedor added >bug :Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one. labels Jul 19, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Distributed/Distributed A catch all label for anything in the Distributed Area. If you aren't sure, use this one.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants