Kibana error on Discover when accessing index pattern with Recently shrunk index

[vvwood (Vince Wood)]

As mentioned in the subject, I have an index pattern that references a recently shrunk index. After the shrink happened, I get the following error.

Wrapper@https://Node1.domain.com:5601/31997/bundles/commons.bundle.js:3:465601
_createSuper/<@https://Node1.domain.com:5601/31997/bundles/commons.bundle.js:3:464389
HttpFetchError@https://Node1.domain.com:5601/31997/bundles/commons.bundle.js:3:467368
_callee3$@https://Node1.domain.com:5601/31997/bundles/commons.bundle.js:3:1287438
l@https://Node1.domain.com:5601/31997/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:288:969217
s/o._invoke</<@https://Node1.domain.com:5601/31997/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:288:968971
_/</e[t]@https://Node1.domain.com:5601/31997/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:288:969574
asyncGeneratorStep@https://Node1.domain.com:5601/31997/bundles/commons.bundle.js:3:1280961
_next@https://Node1.domain.com:5601/31997/bundles/commons.bundle.js:3:1281290

Per this page, the alias in the form of the original index name should have been created and I have confirmed that the alias shows on the index management status page.

So my question is, Any idea what this error means and why it is occurring?

[wylie (Wylie Conlon)]

Two questions:

1. Does the index pattern you have match both the shrink-indexname-* and indexname-* patterns?

2. What does the actual response from Elasticsearch show? You can check in the Network tab of the browser dev tools for the failing request.

[vvwood (Vince Wood)]

Afternoon Wylie,
Yes the index pattern did line up.
I am not currently seeing the same problem so I will need to recreate the symptom before I can answer your second question. As soon as I do, I will provide that info.
-Vince