You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In its-live-monitoring-test, processing the sentinel2-valid-2,json integration test message (shown below) pulls so many potential secondary pairs that the lambda is timing out even when setting the maximum timeout of 15 minutes.
The test stack is much more verbose, setting the logging level to DEBUG -- it's possible that setting logging to INFO would keep us under the timeout...
But I think that this is currently a blocking issue.
The text was updated successfully, but these errors were encountered:
Switching from DEBUG to LOG logging level in the test environment brought this down to just over 5 minutes, and sentinel2-valid-1.json ran in 1.5 minutes.
I will leave this open to monitor over time as we'll probably want to address it, but this is not a blocking issue anymore. We can monitor and determine how often this is a real problem.
Another strategy would be to reduce the search bounding box so that it doesn't overlap with neighbor tiles, significantly reducing the number of results to check.
In
its-live-monitoring-test
, processing thesentinel2-valid-2,json
integration test message (shown below) pulls so many potential secondary pairs that the lambda is timing out even when setting the maximum timeout of 15 minutes.The test stack is much more verbose, setting the logging level to DEBUG -- it's possible that setting logging to INFO would keep us under the timeout...
But I think that this is currently a blocking issue.
The text was updated successfully, but these errors were encountered: