This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-20
Channels
- # admin-announcements (28)
- # aws (16)
- # beginners (70)
- # boot (54)
- # cider (86)
- # cljsrn (8)
- # clojure (14)
- # clojure-art (12)
- # clojure-conj (2)
- # clojure-hk (45)
- # clojure-nl (2)
- # clojure-poland (2)
- # clojure-russia (32)
- # clojurescript (60)
- # cursive (27)
- # datomic (12)
- # devcards (46)
- # editors (2)
- # emacs (37)
- # immutant (72)
- # jobs (6)
- # ldnclj (7)
- # leiningen (1)
- # off-topic (1)
- # om (205)
- # onyx (16)
- # re-frame (21)
- # reagent (52)
- # slack-help (2)
- # spacemacs (11)
hey @lucasbradstreet , we had what looks like a leak situation again. i don’t have the time now to dig into it, but sharing it with you as we discussed
Thanks. Still no retries, but latency is spiking?
Do you track "complete latency" anywhere in there?
the yellow line in INPUT is 99.9 complete latency
a restart fixed it
Wow. So 40K being 40 second complete latency
So basically it got quite close to being retried
what’s weird is that the complete latency recovered but all the individual tasks were spiking up and down like that
which suggests some sort of GC churn again
Hmm. Flight recorder would be able to tell you whether it's GC related. If all the tasks are spiking together you might be right
i’ll definitely get JMX stuff going next week
have a great weekend
Cool. Let us know when you know more. Really want to get this one solved for you
You too