-
Title
After selecting 'Earliest Available' data range, 7day queries timeout -
Description
We received a 60 second timeout when generating 7day queries on any dashboards. We discovered this was only after previously selecting the ''Earliest Available' checkbox which had completed sucessfully. If one logs out after the dashboard timeout, then the subsequent login will generate any dashboard 7day query successfully (ie. Java EE Requests completes in 35 seconds).
-
Cause
The ''Earliest Available' query although appears complete in the initiating dashboard, is still running populating cache with all data from Jan 1 2000 for all dashboards which use a timezone zonar.
-
Resolution
One should use Reporting when selecting data from the beginning of data collection since that action will not populate the cache for all the other dashboards which use a timerange zonar.
If you choose to use the 'Earliest Available' checkbox for your current dashboard, then logging out of the Web Console will terminate the query to populate all of cache.Here's the explanation which describes what actually is taking place.After selecting the Earliest Available checkbox, when it appears the request is finished for your current dashboard, the process is in fact still running to dump ALL data to cache for availability for each dashboard which has a range zonar. Any subsequent query is then in the queue and will most likely timeout until the previous request has completed dumping all data to the cache.
This is the same for any zonar change where cache is populated with the data for all dashboard with a zonar since one is changing the scope of data view for the product.