We see this behavior when we ask it to do a Hovmoller plot or any plot that spans multiple years. Today our servers aren't seeing as much use, and the Hovmoller for ODYSSEA barely squeaked to finish right before the 300 second mark -- most of the time, it can't complete 1 year of data by 300 seconds.
Here's an example using OSTIA; it, too, has the same behavior but spans a longer time and thus is sure to not complete in 300 seconds.
The link to OSTIA is here:
Here is an example of trying to do a time series:
Meanwhile I can watch the logs scroll along as the backend continues to open up the rest of the granules in the request.
The exact time span that completes in under 300 seconds varies depending on how much traffic the site is receiving; and of course, all the job requests where the front end fails after 300 seconds are still there and contributing to the load in the background, making the next request even more tight on the time-range that will complete.
Thank you for looking into this.
From: Roland Schweitzer - NOAA Affiliate [roland.schweitzer@xxxxxxxx]
Sent: Friday, April 05, 2013 12:46 PM
To: Shelton, Kacie E (398C)
Cc: las_users@xxxxxxxx; Sumagaysay, Rosanna M (3980-Affiliate)
Subject: Re: [las_users]
Now I'm really confused.
This data set works like a champ though there seems to be some missing data in the middle. I'm making plots of all the different variables and the first, last and some random time steps in between and they all work and return in a matter of a couple of seconds.
And this is the full data set that fails after 300 seconds on your server?
On Fri, Apr 5, 2013 at 12:58 PM, Shelton, Kacie E (398C) <kacie.e.shelton@xxxxxxxxxxxx> wrote: