Field type conflict where indices with conflicting type do not exist

[adamsm]

Hi

We run Kibana on AWS. We are seeing Field type conflict on a few fields, see an example image below:

However we have a stack management policy which has already deleted the conflicting indices in question (those of type string).

I have confirmed the indices in question do not exist by running the following:

GET /log-collector-2021-09-27

Response:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "index_not_found_exception",
        "reason" : "no such index [log-collector-2021-09-27]",
        "index_uuid" : "_na_",
        "resource.type" : "index_or_alias",
        "resource.id" : "log-collector-2021-09-27",
        "index" : "log-collector-2021-09-27"
      }
    ],
    "type" : "index_not_found_exception",
    "reason" : "no such index [log-collector-2021-09-27]",
    "index_uuid" : "_na_",
    "resource.type" : "index_or_alias",
    "resource.id" : "log-collector-2021-09-27",
    "index" : "log-collector-2021-09-27"
  },
  "status" : 404
}

and

GET _cat/indices?v

and then searching for the problematic indices (I have not been able to find them).

I have also tried recreating the indices with the correct field types long. However this did not help either.

I am at a loss, does anyone have any ideas?

[bhavyarm]

@mattkime can we please get some help here?
Thanks,
Bhavya

[mattkime (Matthew Kime)]

@adamsm Which version of the stack are you running? If you're running a version where you can manually refresh the field list, does refreshing the field list fix the problem?

[adamsm]

Hi @mattkime

Thanks so much, we are running v7.10.2 which does have the ability to refresh the field list. This did solve the issue. Much appreciated.

[mattkime (Matthew Kime)]

@adamsm Glad to hear! Newer versions refresh the field list automatically which would have prevented this confusion.