-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: Use the database while trying to reconnect to Redis #1669
Conversation
The retries were reduced in order that the user get the data more quickly. Solves #1430
}) | ||
|
||
const lockManagers: Record<Priority, LockManager> = { | ||
[Priority.Low]: createLockManager({ | ||
retryCount: 0, | ||
}), | ||
[Priority.High]: createLockManager({ | ||
retryCount: 10, | ||
retryCount: 5, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The retry was reduced (also at line 31 maxRetriesPerRequest: 3,
it is by default 20) in order that the user don't wait that much
error, | ||
location: 'Cache lockManager', | ||
}) | ||
client.disconnect() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since it will keep logging from the line 34, we don't need two or three sentry events for the same problem, so, disconnecting stop logging from the lock manager.
Besides that, it keeps logging to Sentry, which should warn us.