How to query elasticsearch: I keep getting index_not_found_exception


(Jose) #1

Elasticsearch 6.4.3

Issue: /_search command returns:

index_not_found_exception

Specifically:

$ curl -X GET "192.168.2.2:9200/MyNew_Index/_search" -H 'Content-Type: application/json'
{
"from": 0,
"size": 40,
"sort":
...

Returns:

{
    "error": {
        "root_cause": [{
            "type": "index_not_found_exception",
            "reason": "no such index",
            "resource.type": "index_or_alias",
            "resource.id": "MyNew_Index",
            "index_uuid": "_na_",
            "index": "MyNew_Index"
        }],
...

But when I look to see what indexes are present, I see it:

$ curl -X GET "192.168.2.2:9200/_cat/indices?v" -H 'Content-Type: application/json'
health status index                          uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   MyNew_Index 71X8IOLzQaKqj7aaK5CRbA  50   1  900288822
3322978        1tb        533.4gb

What am I missing?


(Mark Walkom) #2

What does _cat/indices/MyNew_index?v show?


(Jose) #3
curl -X GET "192.168.2.2:9200/_cat/indices/MyNew_index?v" -H 'Content-Type: application/json'

health status index                          uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   MyNew_index 71X8IOLzQaKqj7aaK5CRbA  50   1  901322309
3449192        1tb        534.7gb

(Jose) #4

Is it possible that certain index names are problematic?

What about an index name of: 2018_v2_NEW_CLUSTER_Case_61123


(Mark Walkom) #5

I've seen it on a few occasions in the past but it's super rare and usually extremely hard to cause.


(Jose) #6

OK, what should I do next? (This is a production index, the .NET code has no trouble getting to it, but I am stuck on the interactive side...)


(system) #7

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