Re: Blocked thread

References	<CACwCsY7BWeV14+=OHbgYyfwV8qGkTv_nRC4e4+Ahxv3+RP+tng@mail.gmail.com> <CAPTjJmpi8d28ahbba0LNQU8rY4r0EvwUmDS2zRMVsUn0tubtuQ@mail.gmail.com> <CANc-5UyPjdozTKjOzOy6H=Ar3_Jzx1MU68qymyEoFWx7p_piEQ@mail.gmail.com> <CACwCsY54hxnRHainr7Mk6T=tEosTC2ja-pk7=_6QL11MKsD3+g@mail.gmail.com>
Date	2014-07-18 04:04 +1000
Subject	Re: Blocked thread
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.11941.1405620258.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Fri, Jul 18, 2014 at 4:00 AM, Larry Martell <larry.martell@gmail.com> wrote:
> I did ask my DBA - he said "Blocking is a normal part of database
> operations. It's only a problem when it's a deadlock, in which case
> the server will detect that, kill one of the processes and log it."
>
> My situation is not a deadlock - there's just multiple scripts hitting
> the same tables at the same time. When one gets done the next one
> proceeds. I just want to find out what are the other processes causing
> this.

Then you definitely want server-side info. The DB server's the one who
knows who's waiting on whom. See if your DBA can help you with the
specifics; this will be bread-and-butter monitoring work for him.
Automating it might require some tweaking, but if he's at all
competent at his job, he'll know how to figure out (if manually)
what's blocking an important query.

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Blocked thread Chris Angelico <rosuav@gmail.com> - 2014-07-18 04:04 +1000

csiph-web