Open matus-hodul opened 4 weeks ago
Adding on that I've also been noticing more of this "oops" error come up intermittently (although now I'm getting it more permanently). It was originally reported here in this thread.
Thanks for posting this issue in the repo. We're looking into it, but so far, it doesn't appear to be a CMR-STAC issue but rather something happening upstream with CMR.
Hello, Based on the previous comment, is this still being looked at from the CMR-STAC team? If it's an upstream issue, is there somewhere else we should raise it? This bug has been breaking HLS STAC functionality regularly since the beginning of September - is it possible to revert whatever change was made at that time? Thanks!
Hi @waltersdan - These issues appear to be caused by periodic bursts of user-driven activity (e.g., scripts harvesting a large amount of data). We're working alongside our operations and infrastructure teams to identify a solution. I'll post another update here when I have more information on a timeline for resolution.
Ok, thanks for the update!
@aliciaaleman, I've had success with the cloudstac
endpoint vs the stac
endpoint (as noted here).
I understand that the cloudstac
endpoint only contains STAC collections available in the cloud, but is there any reason I should be using stac
instead to get HLSS30.v2.0 metadata? I did a quick test comparing search results (similar to @matus-hodul search params) between both endpoints and didn't see a difference, so I assume using either endpoint is fine.
Other than the update to the collection id, the only difference I see is the API specs.
Conformance Classes OGC OGC API - Features - Part 1 - Core 1.0 OGC API - Features - Part 1 - Oas30 1.0 OGC API - Features - Part 1 - Geojson 1.0 STAC Core v1.0.0-beta.1 Item Search v1.0.0-beta.1 Item Search - Fields v1.0.0-beta.1 Item Search - Query v1.0.0-beta.1 Item Search - Sort v1.0.0-beta.1 Item Search - Context v1.0.0-beta.1
Conformance Classes OGC OGC API - Features - Part 1 - Core 1.0 OGC API - Features - Part 1 - Oas30 1.0 OGC API - Features - Part 1 - Geojson 1.0 OGC API - Common - Part 1 - Simple Query 1.0 STAC Core v1.0.0-rc.2 Item Search v1.0.0-rc.2 Ogcapi Features v1.0.0-rc.2 Item Search - Fields v1.0.0-rc.2 Item Search - Features v1.0.0-rc.2 Item Search - Query v1.0.0-rc.2 Item Search - Sort v1.0.0-rc.2 Item Search - Context v1.0.0-rc.2 Collection Search v1.0.0-rc.2 Collection Search - Free Text v1.0.0-rc.2 Collection Search - Sort v1.0.0-rc.2
We noticed that the HLS “Oops!” error* seems to occur at roughly the same time every day, so we created a script which checks the status of HLS throughout the day. Indeed, the oops error occurs every day around 2 pm pacific time, and lasts for a couple hours, after which it resolves itself. There are other periods of oops error during the day as well, but these are shorter and don’t seem to follow a specific pattern.
* full error is: pystac_client.exceptions.APIError "Oops! Something has gone wrong. We have been alerted and are working to resolve the problem. Please try your request again later."