My kibana dashboard is showing documents that I have since deleted..
To reproduce the issue, create an alias that encapsulates the indices that you will be deleting a document type from and assign it to those indices.
Then, after invoking a delete for the type across the alias like:
curl -XDELETE 'eshost:9200/my_alias/my_type_to_delete'
Notice that the type is deleted from the alias'd indices but kibana will still display the documents in it's quick search across whatever time range you have.
Drilling deeper into a specific time range however will result in:
"Courier Fetch: 1 of X shards failed"
The reason provided for the failure in the response (obtained via the developer console in chrome) is: "NullPointerException[null]" for an index that I can confirm no longer has the type that was deleted.
As far as I understand it, Kibana should just be visualizing what's coming from the ES backend so I'm not sure why it would behave this way... please advise.
Edit: my workaround has been to do a "Delete by Query" which I would think should be unnecessary after the first deletion using the alias
Edit 2: it may be worth additionally noting that while deleting by query seems to clean up the problem for specific indices, trying to do the same query-style deletion does not work when using my alias (which I can confirm points to the correct indices)