-
Bug
-
Resolution: Done
-
Minor
-
None
In the past hours, we've had four occurrences of this Exception on Trino.
TrinoStatementExecErrormasu.processor.tasks.update_summary_tables
Error opening Hive split s3a
...
The specified key does not exist.
TrinoExternalError
Error opening Hive split s3a://hccm-prod-s3/data/parquet/daily/1192522/OCP/pod_usage/source=6eb972d3-32fc-4b55-929b-d9232066eab1/year=2024/month=04/pod_usage.2024-04-03.3935223.0_daily_0.parquet (offset=0, length=132369): The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: D0MSPNK38AS9CT2F; S3 Extended Request ID: 4NfegVUBVl9+XylRDcvB5jKn+2OvtwqxOMH7f0i8nLANThCHSXDdCcQu64kZWYLJSMsDUBdhaqQ=; Proxy: null)
I think this closed task is related: https://issues.redhat.com/browse/COST-4624
Link to the alert details: https://glitchtip.devshift.net/insights/issues/3320536?project=83&start=2024-04-02T00:00:00.000Z
- is cloned by
-
COST-5042 [GlitchTip] TrinoStatementExecError: failing to connect
- Closed