Cube.js with Redis IO library returns error during fail over.
Describe the bug
Cube.js with Redis IO library returns error during fail over.
To Reproduce Steps to reproduce the behavior:
- Deploy Redis as a stateful set using sentinel, see: https://github.com/bitnami/charts/tree/master/bitnami/redis
- Connect Cube.js to redis using sentinel.
- Kill Master Pod.
- Wait few seconds for Sentinel to elect a new master.
Expected behavior
Expected Results: Cube.js retries Redis calls and wait a few seconds or skips Redis and queries the source data. Actual Results: Cube.js API return error to the client.
Screenshots If applicable, add screenshots to help explain your problem.
Version: 0.29.21
If you are interested in working on this issue, please leave a comment below and we will be happy to assign the issue to you. If this is the first time you are contributing a Pull Request to Cube.js, please check our contribution guidelines. You can also post any questions while contributing in the #contributors channel in the Cube.js Slack.
👋 a quick reminder that we will be replacing Redis with Cube Store as announced in this blog post.
I believe that this issue is not relevant anymore since Cube Store has replaced Redis for query queue and cache management.
Docs: https://cube.dev/docs/product/deployment#redis
Announcement: https://cube.dev/blog/how-you-win-by-using-cube-store-part-1