Yes. The way I was going to do it was have a gauge that measures how long blocking calls are open for.
I’ll see it in our monitoring system because all of a sudden the send latencies will keep rising per second. On Fri, Apr 17, 2015 at 5:10 AM, Tim Bain <tb...@alumni.duke.edu> wrote: > Also keep in mind that send() is a blocking call, so the stopwatch idea > will only tell you when PFC has occurred and then cleared up (once send() > returns), but won't alert you to a deadlock that won't clear up on its own. > On Apr 17, 2015 6:06 AM, "Tim Bain" <tb...@alumni.duke.edu> wrote: > > > There's a log line in the broker whenever PFC kicks in; we watched the > > logs for that line and fire off an email to get someone to investigate. > > Would that meet your needs? > > On Apr 16, 2015 10:10 PM, "Kevin Burton" <bur...@spinn3r.com> wrote: > > > >> I’m looking at implementing producer flow control so that I don’t fill > up > >> the queues on my broker. > >> > >> It doesn’t look like there’s any way I can see that a client is > blocking, > >> waiting for resources to be released. > >> > >> Maybe one strategy could be to put a stopwatch around each send() and > then > >> I can see that I have some outstanding that have been open for a long > >> time. > >> > >> > >> -- > >> > >> Founder/CEO Spinn3r.com > >> Location: *San Francisco, CA* > >> blog: http://burtonator.wordpress.com > >> … or check out my Google+ profile > >> <https://plus.google.com/102718274791889610666/posts> > >> <http://spinn3r.com> > >> > > > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
