MySQL Gone Away Error
Bug #716652 reported by
Rick Harris
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
Medium
|
Rick Harris | ||
Bug Description
If the registry runs long enough you'll end up with a MySQL Gone Away Error.
This is because MySQL, by default, will close a connection after 8 hours and SQLAlchemy keeps ConnectionPool connections open forever.
We can tell SA to periodically close the connections using the `pool_recycle` option.
A sensible default is probably 3600 (1 hour), though in production, if you know your MYSQL config, you probably want to set it to the full 8 hours.
Related branches
lp:~rconradharris/glance/bug716652
- Jay Pipes (community): Approve
-
Diff: 71 lines (+38/-1)3 files modifiedetc/glance.conf.sample (+9/-0)
glance/common/config.py (+21/-0)
glance/registry/db/api.py (+8/-1)
| Changed in glance: | |
| assignee: | nobody → Rick Harris (rconradharris) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| Changed in glance: | |
| status: | In Progress → Fix Committed |
| Changed in glance: | |
| milestone: | none → 2011.2 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
