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
I'd like to understand how strict trino is with keeping the actual file system cache's size within the configured limit. We are running trino in kubernetes and have mounted an ephemeral volume with a maximum size of 10Gi. We configured trino to use at most 9G for the file system cache. Still we see that the pod would get evicted from time to time with a message like:
Usage of EmptyDir volume "fs-cache" exceeds the limit "10Gi"
So it looks like 1Gi of headroom isn't enough?
For a local test, I've reduced the max cache size to 9Mb.
We actually have 2 connectors and configure them individually like this:
The only thing that I could read in their code is:
// We assume there will be some overhead using local fs as a page store,
// i.e., with 1GB space allocated, we
// expect no more than 1024MB / (1 + LOCAL_OVERHEAD_RATIO) logical data stored
Hi,
I'd like to understand how strict trino is with keeping the actual file system cache's size within the configured limit. We are running trino in kubernetes and have mounted an ephemeral volume with a maximum size of 10Gi. We configured trino to use at most 9G for the file system cache. Still we see that the pod would get evicted from time to time with a message like:
So it looks like 1Gi of headroom isn't enough?
For a local test, I've reduced the max cache size to 9Mb.
We actually have 2 connectors and configure them individually like this:
and
After running and querying for a while I can already see that the sizes are exceeded a bit:
I've also observed that sizes went down a bit from time to time. I'm unsure though what amount of headroom we should grant the cache?
The text was updated successfully, but these errors were encountered: