enable configurable timeout of openUrl

Issue #567 resolved
Reimar Bauer created an issue

We could move the timeout=30 as a default to MissionSupportSystemDefaultConfig and make it configurable
https://bitbucket.org/wxmetvis/mss/src/develop/mslib/ogcwms.py#lines-78

This is not an API change so we could do this for 1.9.4.

Comments (7)

  1. Joern Ungermann

    Making this configurable seems reasonable.

    However, I’d like to point out, here, that ideally the MSWMS server should be configured in a way that it needs less than 30s to assemble the capability document. The CachedDataAccess class was written to speed up the data discovery.

    If some server setup cannot be brought down in time, we should speed up the server/provide a configuration option for the server to be faster.

    My post-campaign servers with global data for several months and dozens of layers servers the document in seconds due to the CachedDataAccess class…

  2. Reimar Bauer reporter

    making this configurable has also the benefit that we can have a shorter timeout in tests.

  3. Shawn Honomichl

    Joern and Reimar,

    Thanks for working on this. I do like the configurable timeout idea. Currently we are only keeping a days worth of model output for WACCM and GEOS-5 and it is still timing out. I think this is likely because of the way that our MSS server is set up and accessing the model output. We basically have a computer system that hosts several (or more for all I know) virtual servers on the same small machine, and the data is being accessed from a different remote machine that has enough space to house the model data. Unfortunately, this remote machine that is holding the data is very heavily used, which also does not help.

    -Shawn Honomichl

  4. Shawn Honomichl

    Thanks Reimar and Joern,

    I think between the CachedDataAccess and setting the timeout up a little bit, we have solved our issue!

    -Shawn

  5. Log in to comment