Visualize: Bad Gateway & Courier Fetch (shards failed)

Elastic Stack Kibana
1

I'm using Kibana's (5.4.0) and while trying to access Dashboard for 30 days, I'm getting following (red) error:

Error: Bad Gateway
    at respond (https://foo.bar/bundles/kibana.bundle.js?v=15063:13:2730)
    at checkRespForFailure (https://foo.bar/bundles/kibana.bundle.js?v=15063:13:1959)
    at https://foo.bar/bundles/kibana.bundle.js?v=15063:1:28418
    at processQueue (https://foo.bar/bundles/commons.bundle.js?v=15063:38:23621)
    at https://foo.bar/bundles/commons.bundle.js?v=15063:38:23888
    at Scope.$eval (https://foo.bar/bundles/commons.bundle.js?v=15063:39:4619)
    at Scope.$digest (https://foo.bar/bundles/commons.bundle.js?v=15063:39:2359)
    at Scope.$apply (https://foo.bar/bundles/commons.bundle.js?v=15063:39:5037)
    at done (https://foo.bar/bundles/commons.bundle.js?v=15063:37:25027)
    at completeRequest (https://foo.bar/bundles/commons.bundle.js?v=15063:37:28702)

_cat/thead_pool: (while accessing)

foo bulk                1 0  0
foo fetch_shard_started 0 0  0
foo fetch_shard_store   0 0  0
foo flush               0 0  0
foo force_merge         0 0  0
foo generic             0 0  0
foo get                 0 0  0
foo index               0 0  0
foo listener            0 0  0
foo management          1 0  0
foo refresh             2 0  0
foo search              0 0  0
foo snapshot            0 0  0
foo warmer              0 0  0

yet with 7 days, I'm getting (yellow) error:

Courier Fetch: 55 of 145 shards failed.

/var/log/elasticsearch/elasticsearch.log @pastebin.com

Please advise.
Thanks in advance!

2

What does ES show in the logs at this time?

4

I updated my topic with output from elasticsearch.log.

5 
Caused by: java.lang.IllegalArgumentException: Fielddata is disabled on text fields by default. Set fielddata=true on [shopId] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.

You need to update your mappings as the error suggests :slight_smile:

6

per my mapping shopId already set as keyword type:

      "shopId": {
        "type": "keyword"
      },
7

after I _reindex all of my indices, previous error that was appearing in logs before went away, however

Visualize: Request Timeout after 30000ms

still showing up on top of screen, and I'm not seeing anything in logs when I get an error...

8

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