-
Notifications
You must be signed in to change notification settings - Fork 79
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
[Transaction Stream Service] [CACHE WORKER] Failed to update the latest version in the cache. Version is not right. #648
Comments
When you see this error, can you check if the "latest_version" is still in redis? |
This is what I see
|
This aligns with my guess. For some reason, the "latest_version" got evicted from redis, which will cause the error. You can manually set the "latest_version" back to recover. |
Yes, setting back the
...
I have doubled the memory (32G->64G) and I am testing if changing the eviction policy makes the
Additionally, I see that there is some logic of active cache eviction here. The threshold is set to 300k keys. I was able to hold 20k with 32GB of ram assigned to redis. Sadly this is |
Description
Cache worker failing to sync from PFN (fails after few hours on random version(s)). Not sure if this is a bug, because the version check looks like intentional health check logic, but maybe there is a way to workaround the version check on redis/cache worker to make the cache worker going?
Repro
aptos node bootstrap-db --ledger-history-start-version 0 --command-adapter-config gcs.yaml --target-db-dir data/db --metadata-cache-dir meta
(aptos cli 4.6.0)The text was updated successfully, but these errors were encountered: