Closed Bug 880102 Opened 9 years ago Closed 9 years ago

Tweaks to get long-query-timeouts working in stage

Categories

(Cloud Services :: Server: Sync, defect)

Product:
Cloud Services
Component:
Server: Sync
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rfkelly, Unassigned)

Details

(Whiteboard: [qa+])

Attachments

(2 files)

patch against upstream PyMySQL release
3.02 KB, text/plain
telliott
: review+
Details
patch to log attempts at query killing
2.02 KB, patch
telliott
: review+
Details | Diff | Splinter Review 
Following up from Bug 879094, we need a couple of tweaks to PyMySQL to get the long-query-timeout-killing thing working properly.  I'm going to take the liberty of committing and tagging so as not to block Ops, but am filing this bug to keep track of everything.

First, I'm attaching a patch that gets applied to the upstream PyMySQL release as part of the build process.  It combines these two upstream bugs into a single patch:

  * https://github.com/petehunt/PyMySQL/pull/148
  * https://github.com/petehunt/PyMySQL/pull/150

I'm not thrilled that these patches are starting to pile up, but at least they're small and simple so far...
Attachment #758929 - Flags: review?(telliott)
Second is a bit of debug logging so that we have visibility into when queries are being killed.
Attachment #758930 - Flags: review?(telliott)
QA Contact: jbonacci
Whiteboard: [qa+]
Comment on attachment 758929 [details]
patch against upstream PyMySQL release

If you're planning to submit this back upstream, recommend you break it out into two: the except changes and the unpack changes.
Attachment #758929 - Flags: review?(telliott) → review+
Comment on attachment 758930 [details] [diff] [review]
patch to log attempts at query killing

Recommend adding the query string to the "unsafe query" log so we have a little more information when it does happen.
(In reply to Toby Elliott [:telliott] from comment #2)
> If you're planning to submit this back upstream, recommend you break it out
> into two: the except changes and the unpack changes.

Yep; see the two independent pull request links above :-)

(In reply to Toby Elliott [:telliott] from comment #3)
> Recommend adding the query string to the "unsafe query" log so we have a
> little more information when it does happen.

http://hg.mozilla.org/services/server-core/rev/ff1d9a20bc76
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Attachment #758930 - Flags: review?(telliott) → review+
You need to log in before you can comment on or make changes to this bug.