This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-19
Channels
- # announcements (9)
- # babashka (5)
- # babashka-sci-dev (23)
- # beginners (160)
- # calva (78)
- # cider (23)
- # clj-commons (2)
- # clj-kondo (5)
- # cljdoc (19)
- # cljs-dev (8)
- # clojure (54)
- # clojure-australia (1)
- # clojure-czech (2)
- # clojure-dev (17)
- # clojure-europe (8)
- # clojure-italy (8)
- # clojure-nl (2)
- # clojure-sg (3)
- # clojure-uk (4)
- # clojurescript (70)
- # community-development (8)
- # core-async (8)
- # cursive (7)
- # datahike (12)
- # datalog (22)
- # datomic (20)
- # events (1)
- # fulcro (43)
- # graalvm (92)
- # gratitude (5)
- # holy-lambda (77)
- # honeysql (1)
- # jobs (1)
- # lsp (111)
- # membrane (70)
- # nextjournal (13)
- # off-topic (73)
- # pathom (1)
- # polylith (8)
- # portal (32)
- # re-frame (3)
- # reagent (4)
- # reitit (5)
- # releases (2)
- # reveal (4)
- # xtdb (22)
I just came here to ask the same thing. Hopefully it can be restored!
Just saw this now (didn’t check my email where alerts go) — restarting 🙂
The machine was at 100% CPU and failed to handle incoming requests.
Does anyone have advice on understanding why this happened how we can understand why it’s happening the next time around? Anecdotally it feels like this wasn’t an issue for a long time but over the last months I probably restarted the service twice.
The obvious default spot to check is the logs. Capturing a thread dump, if possible, before restarting can be helpful.
Can't remember what kind of metrics cljdoc is collecting on itself. If cpu usage is one of them, you could correlate when cpu went high against logs.
The logs basically stop around 8:34pm (UTC) yesterday 😅
@lee I’d be happy to share prod access with you + some guide on how to restart the service
Curious, Cora did trigger a redeploy and that did not work. I wonder why. Maybe the container was pooched?
I think the redeploy will only actually deploy if the sha changes or something like that
It might have worked to push an empty commit or the likes
Basically we publish to docker and when the deploy asks for the same docker image Nomad (the scheduler) will be like “eh; nothing to do here”
@deleted-user I’m assuming this is a joke but just in case it’s not, do you happen to have experience with https://www.nomadproject.io/?
ah that’s cool. I basically just use it to achieve a green/blue type deployment thing where there is no downtime between deploys (vs. systemd or similar)
@deleted-user if you’re interested I’d also be happy to share prod access with you
That’s awesome but I’m also just asking to de-risk the ops part a bit, no expectation that you or someone else necessarily dig into the cpu issue 🙂