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

Using bottleneck options to recover from instance's crash #197

Open
yarinvak opened this issue Jan 11, 2022 · 0 comments
Open

Using bottleneck options to recover from instance's crash #197

yarinvak opened this issue Jan 11, 2022 · 0 comments

Comments

@yarinvak
Copy link

Hello, I would like to further understand what do you mean by "inactivity" when you talk about the timeout option.

And would appreciate if you can help me understand how can I use bottleneck options in the following scenario:
I have a service which runs on multiple instances, and a bottleneck limiter that is configured to store the keys on redis.
I have jobs, which I don't want to set expiration on.

In case one of the instances started handling the job, but then it was restarted and the job wasn't completed successfully -
how can I make sure that when the instance will be restarted, the limiter will not be stuck on a job that can't run anymore? (because only the key exists on redis, but the job itself doesn't exist).
I thought about using the clearDataStore:true option, but I'm afraid that if only one instance is restarted, it will delete the bottleneck state that is used by the other instances.

Maybe I'm missing something in the way I use bottleneck..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant