Last modified: 2014-02-13 22:11:57 UTC
include the debug comment about where search results originated even for empty result sets results pages with results have something like > <!-- Search results fetched via search=[search14], highlight=[search18], suggest=[search15] in 77 ms --> Both intermittent problems where a search should have results and sometimes doesn't and also when you search for something that should return no result (e.g. bang on the keyboard) you end up without any debug comment for the search. (only the comment for overall page load time and apache name is present) We should include as much as we know (who did we try to contact and what did we get back. HTTP status code, connection timeout, etc.) so that end users that are helping gather info on search problems have some real data to provide. This is related to but not the same as bug 43544. This should help some with debugging bug 42423.
This really doesn't matter in Elasticsearch land, nor do we return this data to the client. Marking WONTFIX.
