This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (10)
- # boot (14)
- # cider (80)
- # clara (1)
- # cljs-dev (19)
- # cljsrn (7)
- # clojure (284)
- # clojure-france (4)
- # clojure-italy (57)
- # clojure-poland (8)
- # clojure-russia (10)
- # clojure-spec (65)
- # clojure-uk (155)
- # clojurescript (156)
- # code-reviews (6)
- # copenhagen-clojurians (16)
- # cursive (10)
- # datomic (10)
- # emacs (13)
- # euroclojure (1)
- # graphql (4)
- # jobs (2)
- # lein-figwheel (3)
- # luminus (4)
- # off-topic (2)
- # onyx (42)
- # parinfer (23)
- # pedestal (1)
- # protorepl (8)
- # re-frame (34)
- # reagent (17)
- # ring-swagger (5)
- # timbre (24)
- # vim (72)
- # yada (1)
Datomic 0.9.5561.54 is now available https://groups.google.com/d/topic/datomic/oHBXJkE7cdA/discussion
we're seeing indexing alarms and what looks to me like transactions causing the transactor to timeout and miss heartbeat, causing a failover to the standby transactor. search google and looking at our stats, it appears it's related to our high sustained write volumes (over 500MB during some minutes). would increasing writeConcurrency help with this? if so, what are safe values to try?
I am creating a new datomic in-memory database on every test run, then deleting it, but there seems to be some memory overhead to doing this numerous times
Is anything being kept in memory? e.g. an open connection, or else? And can I release it?
We are seeing this error when upgrading our dynamo-based datomic peer to
0.9.5561.50. Has anyone seen this / can advise?
ClassCastException com.amazonaws.services.dynamodbv2.model.GetItemResult cannot be cast to com.amazonaws.AmazonWebServiceResult datomic.ddb/fn--9598 (ddb.clj:47)
@erichmond what are you upgrading from? What other AWS related dependencies do you have in your project?
Hi Guys, I am interested in running Datomic with Finagle (https://github.com/twitter/finagle). Why?
We are using it on most of our stack (http,thrift,kafka and iso8583)
We benefit from using finagle
In our microservices architecture, pretty much every
port (from ports and adapters) has its own
When we implement our components using finagle, we get circuit-breakers, expo backoff, and self-healing almost for free.
We current have an issue that when a Peer fails to reach the transactor for a long enough time period, we have a
hard trip for our circuit breaker and we need to restart the peer application;
We could implement self-healing and expo-backoff in our own datomic wrapper library, but it could be better if we just had a finagle library wraping datomic component;
To do that, I basically need:
a way to get the transactor host from the
encode and decode data that is being transacted or queried (I believe we use use fressian + edn on datomic, but I couldnt confirm)
Have you heard of anyone doing this or could you tell me if you think that doesnt make any sense?