Clear django_session table
Bug #1466126 reported by
Kevin Stevens
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Medium
|
Steve Lewis | ||
Icehouse |
Won't Fix
|
Undecided
|
Unassigned | ||
Juno |
Fix Released
|
Medium
|
Steve Lewis | ||
Kilo |
Fix Released
|
Medium
|
Steve Lewis | ||
Trunk |
Fix Released
|
Medium
|
Steve Lewis |
Bug Description
Looks like mysql is getting pretty big thanks to the django_session table. These are not automatically cleared and must be manually purged per: https:/
Another cron job?
Changed in openstack-ansible: | |
status: | Confirmed → In Progress |
Changed in openstack-ansible: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/195220 /git.openstack. org/cgit/ stackforge/ os-ansible- deployment/ commit/ ?id=36378c5547a 4c39db98994db61 af68ee433ff943
Committed: https:/
Submitter: Jenkins
Branch: kilo
commit 36378c5547a4c39 db98994db61af68 ee433ff943
Author: Steve Lewis <email address hidden>
Date: Tue Jun 23 18:22:02 2015 -0700
Clear expired Django sessions regularly from DB
A random minute in the 21st hour UTC, daily, was chosen arbitrarily.
That it is run on a single arbitrary host from the set was done to
prevent unnecessary work being done until Bug #1424705 provides us with
a cleaner solution.
Adjusted to run once per day just to be sure that the operation doesn't
lock the table for a meaningful duration.
Making this configurable or tunable does not seem
to be necessary at this time.
Change-Id: I87164926a4d6a6 5d3c9f733d625a2 d4af91c2597 396d1d6a2814925 2dabc5655d)
Closes-Bug: #1466126
(cherry picked from commit 4ab949672428fda