Skip to content
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

Redis unavailability raises uncatched error in backend and makes backend unavailable #382

Open
rhanka opened this issue Oct 18, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@rhanka
Copy link
Member

rhanka commented Oct 18, 2023

when redis is down the following error appears in log :
Error: connect ETIMEDOUT at Socket.<anonymous> (/deces-backend/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:627:28) at Socket.emit (node:events:513:28) at Socket._onTimeout (node:net:580:8) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' }
It should be catched and timestamped as a json log of the backend

Moreover, when this happen, the backend can't handle even a simple search request. This is a bug, redis should only block the bulk api.

@rhanka rhanka added the bug Something isn't working label Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants