This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-07
Channels
- # bangalore-clj (1)
- # beginners (255)
- # boot (29)
- # cider (16)
- # cljs-dev (13)
- # cljsrn (6)
- # clojure (200)
- # clojure-berlin (1)
- # clojure-dev (13)
- # clojure-dusseldorf (6)
- # clojure-greece (1)
- # clojure-india (1)
- # clojure-italy (1)
- # clojure-russia (33)
- # clojure-spec (28)
- # clojure-uk (27)
- # clojurescript (47)
- # cursive (32)
- # data-science (3)
- # datascript (1)
- # datomic (40)
- # emacs (39)
- # events (4)
- # fulcro (55)
- # graphql (16)
- # immutant (2)
- # luminus (2)
- # lumo (5)
- # off-topic (142)
- # onyx (50)
- # portkey (1)
- # re-frame (45)
- # reagent (80)
- # remote-jobs (2)
- # ring-swagger (3)
- # rum (9)
- # schema (3)
- # shadow-cljs (184)
- # spacemacs (3)
- # test-check (4)
- # unrepl (2)
- # yada (5)
That forum software is super slick, nice job
My computer crashed and now I can't start my dev transactor anymore without it crashing. I'm seeing:
Launching with Java options -server -Xms1g -Xmx1g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
Starting datomic:, storing data in: ../data/datomic/data ...
System started datomic:, storing data in: ../data/datomic/data
Critical failure, cannot continue: Heartbeat failed
The logs show :
2017-11-07 10:20:38.670 INFO default datomic.lifecycle - {:event :transactor/heartbeat-failed, :cause :conflict, :pid 4647, :tid 25}
2017-11-07 10:20:38.672 ERROR default datomic.process - {:message "Critical failure, cannot continue: Heartbeat failed", :pid 4647, :tid 23}
2017-11-07 10:20:38.674 INFO default datomic.process-monitor - {:MetricsReport {:lo 1, :hi 1, :sum 1, :count 1}, :HeartbeatMsec {:lo 5001, :hi 5005, :sum 20010, :count 4}, :Alarm {:lo 1, :hi 1, :sum 1, :count 1}, :AlarmHeartbeatFailed {:lo 1, :hi 1, :sum 1, :count 1}, :SelfDestruct {:lo 1, :hi 1, :sum 1, :count 1}, :AvailableMB 628.0, :event :metrics, :pid 4647, :tid 23}
2017-11-07 10:20:38.759 INFO default o.a.activemq.artemis.core.server - AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.4.0 [dc68a7d7-c39c-11e7-9092-12754bafa2ff] stopped, uptime 24.966 seconds
How can I fix this ?
@val_waeselynck Are you able to run a dev txor against a new storage (i.e. move/rename the data dir)
@U05120CBV it works if I start from a clean data dir, I guess data corruption occurred when my machine crashed.
I guessed I'll just restore a backup
Restoring to a clean data dir worked. Thanks @U05120CBV @U06GLTD17!
@val_waeselynck zombie transactor process somewhere? :cause :conflict
can be multiple transactors running without a license that supports HA , otherwise possibly due to the local H2 that backs dev not being robust against many failure cases (not intended for that purpose), i.e. failing without all acked writes to storage having been persisted to disk and not being available.
Hey guys, having an issue retrieving large amounts of nodes using datomic pull. I saw in the documentation that there is a limit of 1000 nodes. How would I use the (limit :attr nil)
syntax is this query here below?
['(pull ?e [* {:pid/a [:db/ident]
:pid/b [:db/ident]
:problem/root [* {:problem/foo [:db/ident]
:problem/bar [:db/ident]}]}])])
we need to pull more than 1000 nodes under problem/root
There's an example in the docs: http://docs.datomic.com/pull.html#limit-expressions
['(pull ?e [* {:pid/a [:db/ident]
:pid/b [:db/ident]
(limit :problem/root nil) [* {:problem/foo [:db/ident]
:problem/bar [:db/ident]}]}])])
still 1000
['(pull ?e [* {:pid/a [:db/ident]
:pid/b [:db/ident]
:problem/root [(limit * nil) {:problem/foo [:db/ident]
:problem/bar [:db/ident]}]}])])
still 1000
['(pull ?e [* {:pid/a [:db/ident]
:pid/b [:db/ident]
:problem/root (limit [* {:problem/foo [:db/ident]
:problem/bar [:db/ident]}] nil)}])])
;syntax error
@U2XL48J00 and I tried the suggested solution to no avail
@U2XL48J00 That limit is in the wrong spot
the last example was pure frustration. First example replaces attr-name
with limit-expr
in the outer map spec. the second example replaces attr-name
with limit-expr
in the list spec. So when you say, in the wrong spot
, what exactly do you mean? (as i understand attr-expr = limit-expr | default-expr
but it does not seem to produce intended effect) Thank you.
and yet it didn't
good idea.
turns out nil
aka no limit doesn't seem to work in this case, but setting a specific number works (in example 1)
thank you!
does not work with d/pull
either
Hi all, looking for a bit of help getting a transactor running on AWS against dynamodb storage. I've created the ddb table using ensure-transactor
, and i've created the cloudformation stack using ensure-cf
, create-cf-template
and create-cf-stack
. I've now got a stack in place, but the ec2 instance it creates just shuts down as soon as it starts; no logs make it into my s3 bucket (although the bucket has been created fine). Can anyone point me in the direction of some resources about debugging this? Thanks
i'm using a t2.small instance, which appears in the list of supported instances in my cf-template.json