-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rubix caching: frequent cache evictions result in failed queries #3580
Comments
There are two problems with eviction we have found:
|
@stagraqubole What are recommended workarounds for this? Is it sufficient to have large enough disk? |
Yes, even a modestly sized disk will minimise the chances of hitting this given LRU files would not be read at the time of eviction. |
New version is a bugfix release. Among other it includes fix for trinodb#3580
New version is a bugfix release. Among other it includes fix for trinodb#3580
New version is a bugfix release. Among other it includes fix for trinodb#3580
New version is a bugfix release. Among other it includes fix for #3580
New version is a bugfix release. Among other it includes fix for trinodb#3580
New version is a bugfix release. Among other it includes fix for trinodb#3580 Co-authored-by: Łukasz Osipiuk <[email protected]>
Fixed with #4551 |
Test setup like in #3494 but
rubix.cache.usage.percentage
was setup to2
. This translates to cache size of ~10GB.Cluster was exercised with the same query as in
https://github.com/prestosql/presto/issues/3494
which reads wholelineitem
(171GB).With such configuration many cache evictions are happening throughout the query execution. This itself is fine and expected. Unexpected is that as a result queries are failing:
Logs of coordinator and worker attached:
coordinator.log.gz
worker.log.gz
Note: Presto was built using Rubix 0.3.6 with qubole/rubix#363 applied.
Eventually system ended up in state as in #3524.
cc: @stagraqubole
The text was updated successfully, but these errors were encountered: