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
Sessions that don't explicitly get cleaned (e.g. if the Yarn Resource Manager fails to call the "cancel" method), then some expired sessions will remain in the database. Those sessions could be cleaned up by running a clean-up command on a regular basis with a cron job. Something like what Django has: https://docs.djangoproject.com/en/dev/topics/http/sessions/#clearing-the-session-store https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-clearsessions
The text was updated successfully, but these errors were encountered:
The "creation_time" column should also be indexed to improve performance for that command.
Sorry, something went wrong.
No branches or pull requests
Sessions that don't explicitly get cleaned (e.g. if the Yarn Resource Manager fails to call the "cancel" method), then some expired sessions will remain in the database. Those sessions could be cleaned up by running a clean-up command on a regular basis with a cron job. Something like what Django has:
https://docs.djangoproject.com/en/dev/topics/http/sessions/#clearing-the-session-store
https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-clearsessions
The text was updated successfully, but these errors were encountered: