Closed Bug 1063284 Opened 11 years ago Closed 11 years ago

Log at higher level when killing interrupted sql commands

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rfkelly, Assigned: rfkelly)

Details

(Whiteboard: [qa+])

Attachments

(1 file)

We currently log some DEBUG-level messages when killing a mysql query due to timeout. They don't show up in production logs by default. This should be rare enough and is useful enough to know about, that it's worth logging at WARN instead.
Whiteboard: [qa+]
This patch switches all the relevant log statements from "debug" to "warn".
Attachment #8487642 - Flags: review?(dan.callahan)
Comment on attachment 8487642 [details] [diff] [review] sync-log-at-higher-level-on-query-kill.diff Review of attachment 8487642 [details] [diff] [review]: ----------------------------------------------------------------- LGTM
Attachment #8487642 - Flags: review?(dan.callahan) → review+
https://github.com/mozilla-services/server-syncstorage/commit/30afe77afd9947b268f91b9f3a9c7bd9540c3df1 Bob, this should allow logs about killing mysql queries to appear in production, so we should start watching out for them to get a feel for what frequency etc is.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
(In reply to Ryan Kelly [:rfkelly] from comment #3) > Bob, this should allow logs about killing mysql queries to appear in > production, so we should start watching out for them to get a feel for what > frequency etc is. Excellent. When the next version is rolled out, we'll add it to the Sync app log graphs.
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: