Discover issues numerous msearch queries against indices that do not exist for time patterned indices

[ppf2]

Not sure if this one is also related to (or will be resolved by) #4342.

When using "Use event times to create index names" with hourly logstash indices, if the user selects a time range that is too broad, it goes and attempts to issue numerous msearch queries one for each hour (or for each hourly index) for the past X years (if that's how far back the user selects), even though (in this test case), there are only 2 hourly indices present in the cluster. So as long as the user stays on the Discover screen, Kibana will keep firing off thousands of msearch queries in an attempt to build the histogram - but there are only 2 hourly indices here (and each index has a single event).

Shouldn't it only issue msearch queries against indices that exist in the cluster?

[rashidkpc]

Yes, this will be closed by #4342