Unable to create index in Elasticsearch 7.5.0

Elastic Stack Elasticsearch
1

This is related to the issue I raised before.
While investigating I found that I am having issues in creating a simple index also. And it seems that the install is messed up in some way. The local install does not create any issues.
Any settings which I can tweak?

[elastic@my-linux-machine logs]$ curl -X PUT "http://my-linux-machine:9200/publications?pretty"
{
  "error" : {
    "root_cause" : [
      {
        "type" : "mapper_parsing_exception",
        "reason" : "Root mapping definition has unsupported parameters:  [_all : {enabled=false}]"
      }
    ],
    "type" : "mapper_parsing_exception",
    "reason" : "Failed to parse mapping [_default_]: Root mapping definition has unsupported parameters:  [_all : {enabled=false}]",
    "caused_by" : {
      "type" : "mapper_parsing_exception",
      "reason" : "Root mapping definition has unsupported parameters:  [_all : {enabled=false}]"
    }
  },
  "status" : 400
}

And another thing, nothing is getting logged in the logs !!

Version info:

  "version" : {
    "number" : "7.5.0",
    "build_flavor" : "default",
    "build_type" : "rpm",
    "build_hash" : "e9ccaed468e2fac2275a3761849cbee64b39519f",
    "build_date" : "2019-11-26T01:06:52.518245Z",
    "build_snapshot" : false,
    "lucene_version" : "8.3.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
2

The error clearly states that the error is due to unsupported parameter _all. _all field was deprecated in elasticsearch version 6 and is completely removed from version 7. So You do not need to mention _all : {enabled=false} in mapping definition while creating the index. Here you can look the breaking changes.

3

Hi,

I was trying to put in a simple index without any mappings. Just to test out things.
I am assuming that the mappings if not provided will lead to ES 7.5 putting in a default mapping without the _all

4

No, that should not be the case. If you simply use the below request then a new index will be created successfully with default settings.

PUT test

This will create a new index named as test.

If you then make the bellow request to get the mapping of test index

GET test/_mapping

You'll get the below output:

{
  "test" : {
    "mappings" : { }
  }
}

As you can clearly see that index is created with blank mapping, there could be some other reason for the error that you are getting.

Can you provide the complete request that you are making to create the index.

5

I cant get kibana up and running because of this error. Hence I am using terminal to issue commands.

[elastic@my-linux-machine ~]$ curl -X PUT "http://my-linux-machine:9200/test?pretty"
{
  "error" : {
    "root_cause" : [
      {
        "type" : "mapper_parsing_exception",
        "reason" : "Root mapping definition has unsupported parameters:  [_all : {enabled=false}]"
      }
    ],
    "type" : "mapper_parsing_exception",
    "reason" : "Failed to parse mapping [_default_]: Root mapping definition has unsupported parameters:  [_all : {enabled=false}]",
    "caused_by" : {
      "type" : "mapper_parsing_exception",
      "reason" : "Root mapping definition has unsupported parameters:  [_all : {enabled=false}]"
    }
  },
  "status" : 400
}

As I outlined in my previously raised issue , all my indices have this

"mappings" : {
  "_all" : {
    "enabled" : false
  },
  "properties" : {
    "@timestamp" : {

I am not sure about the sequence of events and hence will not blame anyone. But the upgrade assistant did say all clear. Maybe I did not use it the right way.

My thinking is that presence of these indices with this _all in mapping is causing the ES 7 to act up.

I tried by closing all the existing indices. And then tried to create a sample index but of no avail.

I can extract the mapping of the existing indices via python client and remove the _all section from it. But it is not allowing me to put in an index with this updated mapping also. So option of reindexing the existing indices into new indices with correct mapping is also not available to me.

6

I understand its Holiday season but still hoping someone from Elastic team can chime in.

7

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.