account-reaper does not have an except/log global catchall
Bug #644075 reported by
gholt
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
account-reaper does not have an except/log global catchall. Without such a catchall, uncaught exceptions send full tracebacks to stdout, which skips right over the "clean up common exceptions" code in the logger.
| Changed in swift: | |
| assignee: | nobody → clayg (clay-gerrard) |
| Changed in swift: | |
| assignee: | clayg (clay-gerrard) → nobody |
| Changed in swift: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| Juan J. Martínez (jjmartinez) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to swift (master) | #2 |
| Changed in swift: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to swift (master) | #3 |
| Changed in swift: | |
| status: | In Progress → Fix Committed |
| Changed in swift: | |
| milestone: | none → 1.6.0 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm getting account-reaper errors such as:
- account-reaper STDOUT: error: [Errno 111] ECONNREFUSED / csstore2 account-reaper STDOUT: Removing descriptor: <NUMBER_HERE>
- account-reaper STDOUT: Timeout: 10 seconds
- csstore2 account-reaper STDOUT: BadStatusLine / csstore2 account-reaper STDOUT: Removing descriptor: <NUMBER_HERE>
All of them on direct_
I see this bug report it's just to catch those, but... is it possible that there errors can kill the performance of a 4 storage node cluster? Should a report a new bug for that?
Thanks.