I think increasing the memory limit for your files service would be an appropriate step, you could add reference in the transformers: section of your kustomization.yaml to do this, with the file having the following contents (the default is 1Gi): --- apiVersion: builtin kind: PatchTransformer metadata: name: sas-files-limits-patch patch: |- - op: replace path: /spec/template/spec/containers/0/resources/limits/memory value: 2Gi target: name: sas-files kind: Deployment The files service stores file content in the SAS Infrastructure Data Server as large objects, as well as file metadata like the file ID, content ID, file name, etc in it's database tables. The error message "ERROR: large object ####### does not exist" suggests the files service created the metadata for a file object in the database, but the actual file contents are not present in the database. This could be an artifact of the pod being killed during the file storage process. If a process requests the file content (/files/files/{file_id}/content endpoint), the files service will attempt to retrieve those contents and if the large object is not present, the error above will occur. In this case, the requests for the contents appear to be coming from sas.catalog and sas.searchIndex. Usually these errors don't cause any problems, except that the file content is not available and the request for that content would be returned an HTTP 500 response.
... View more
