We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Lock ages out
Places Nautobot in a deadlock state for get-next-prefix
https://github.com/nautobot/nautobot/blob/v1.4.1/nautobot/ipam/api/views.py#L143 Set a configurable timeout that defaults to 300 seconds. A user should never be able to hit 5 minutes in an API call which would safely add the safe measure. And after 5 minutes if the lock is not gracefully released it will be aged out.
The text was updated successfully, but these errors were encountered:
Resolved nautobot#2350 - Add ability to age out a redis lock
7ed1dae
Resolved #2350 - Add ability to age out a redis lock (#2356)
2f5f218
* Resolved #2350 - Add ability to age out a redis lock * Update nautobot/docs/configuration/optional-settings.md Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com> * addressing feedback * updates from feedback * resolving black Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
Add release-notes for #2307,#2342,#2347,#2349,#2350,#2360
3f72e5c
Successfully merging a pull request may close this issue.
Environment
Steps to Reproduce
Expected Behavior
Lock ages out
Observed Behavior
Places Nautobot in a deadlock state for get-next-prefix
Proposed Fix
https://github.com/nautobot/nautobot/blob/v1.4.1/nautobot/ipam/api/views.py#L143
Set a configurable timeout that defaults to 300 seconds. A user should never be able to hit 5 minutes in an API call which would safely add the safe measure. And after 5 minutes if the lock is not gracefully released it will be aged out.
The text was updated successfully, but these errors were encountered: