This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-17
Channels
- # announcements (1)
- # babashka (94)
- # beginners (76)
- # calva (24)
- # cider (24)
- # clj-kondo (1)
- # cljs-dev (16)
- # cljsrn (45)
- # clojure (135)
- # clojure-europe (9)
- # clojure-france (5)
- # clojure-germany (2)
- # clojure-italy (12)
- # clojure-losangeles (13)
- # clojure-nl (3)
- # clojure-portugal (54)
- # clojure-uk (20)
- # clojurescript (55)
- # conjure (67)
- # core-async (5)
- # cursive (2)
- # datomic (10)
- # docker (7)
- # duct (22)
- # emacs (16)
- # fulcro (34)
- # graalvm (15)
- # hoplon (1)
- # instaparse (1)
- # jobs-discuss (3)
- # juxt (94)
- # luminus (1)
- # meander (4)
- # off-topic (13)
- # pathom (4)
- # pedestal (1)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (61)
- # spacemacs (17)
- # specter (2)
- # sql (23)
- # xtdb (33)
We were running an import of data into a Datomic Cloud solo instance and it appears to have crashed. CPU is stuck at 0%. All calls to d/connect results in a Connect Timeout. Is there no health check that can detect and cycle the process/vm in a case like this?
Last log line
{"Gcname":"G1 Old Generation","Gcaction":"end of major GC","Gccause":"Allocation Failure","Msg":"GcEvent","Duration":5584,"Type":"Event","Tid":8,"Timestamp":1587119656023}
i'm interested as well. recently i discovered that one node in my query group had been completely wedged from a bad query, and i only discovered it hours later when a routine code deployment failed due to inefficient memory.
when I retrieve a db.type/uri
datom from datomic cloud using pull
it comes back with an unexpected class
com.cognitect.transit.impl.URIImpl`.
I was sort of hoping for a
I know I can manually convert it into a http://java.net.URI using str
, my question is whether this is expected behaviour, or whether I have something misconfigured
or should I be de-transiting the response from pull
im also using :db.type/uri
attrs, but only thru on-prem peers.
i would definitely expect it to work on the cloud version too, out of the box.
so, my guess is that it's a bug.
Hey @U793EL04V did you ever find an answer to this? I'm facing the same situation at the moment.
ooh thats quite a while ago.
No, I don't think I solved this; I talked myself into eliminating the :db.type/uri
datom instead,
I see, thank you for your response.
I assume you replaced it with :db.type/String
? Was there any other gotcha like this?