Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-11-10

Channels

#datomic
<
2022-11-10
>
fmnoise17:11:09

Hi everyone, I have a question about serial/parallel transactions processing. If I have multiple databases running on single transactor, does it makes it any possible to runs txs in parallel to separate dbs?

fmnoise17:11:31

I remember datomic transactions are not parallel by design to omit locks and other complicated stuff, but still curious if it's per db or for the whole transactor

fmnoise17:11:28

thanks 🙏

Joe Lane17:11:19

Not sure if you're planning to use on-prem or cloud, but I recommend reading this post and making sure what you're planning to do aligns with the recommendations from marshall and rich https://forum.datomic.com/t/multi-tenancy-databases/238

🙏 1
fmnoise17:11:40

it's on-prem

jjttjj18:11:18

I followed the datomic cloud setup guide, but when attempting to connect to the system I get an error 

;;; deps.edn
{:deps
 {com.datomic/dev-local    {:mvn/version "1.0.243"}
  com.datomic/client-cloud {:mvn/version "1.0.119"}}
 :mvn/repos {"datomic-cloud" {:url ""}}}


(def client1 (d/client {:system      "mysystem1234"
                     :server-type :ion
                     :region      "us-east-1"
                     :endpoint    ""}))


ExceptionInfo Unable to connect to 
{:cognitect.anomalies/category :cognitect.anomalies/unavailable,
 :cognitect.anomalies/message  "DNS timeout 5000 ms",
 :config                       {:system       "mysystem1234",
                                :server-type  :cloud,
                                :region       "us-east-1",
                                :endpoint     "",
                                :endpoint-map {:headers     {"host" ""},
                                               :scheme      "http",
                                               :server-name "",
                                               :server-port 8182}}}
Any tips on how to start debugging this?

Joe Lane18:11:22

Check your template outputs via aws cloudformation describe-stacks --stack-name <compute-stack> and look for your ClientApiGatewayEndpoint in the output and grab the https url value. Replace your 

""
with the ClientApiGatewayEndpoint.

Joe Lane18:11:52

Also, can you provide a link to the "setup guide" you're following?

Joe Lane18:11:06

Reading through https://docs.datomic.com/cloud/tutorial/client.html describes the ClientApiGatewayEndpoint .

jjttjj18:11:51

I was looking at https://docs.datomic.com/cloud/getting-started/start-system.html I don't seem to have ClientApiGatewayEndpoint in the compute stack output

jjttjj18:11:12

(This is using solo topology by the way)

Joe Lane18:11:26

there is no such thing as a solo topology anymore, we consolidated solo+production topology while supporting scaling down to the original "solo" size (and cost).

jjttjj19:11:23

Strange, it's still listed as an option when you step through the aws marketplace listing

jjttjj19:11:05

Ohhh or do you mean that solo now just refers to a smaller sized instance (etc)

Joe Lane19:11:12

ugh... so frustrating. I'll give you the right link

Joe Lane19:11:14

Once you "subscribe" to datomic-cloud in the aws marketplace you can create a system by using the storage and compute stacks under the "Current Releases" section of that link.

jjttjj19:11:07

Gotcha, will give that a try, thanks!

Joe Lane19:11:54

If you get stuck again please reach out. (unfortunately we are currently unable to remove the solo topology from the drop-down in the aws marketplace)

jjttjj19:11:07

That worked, thanks! Small point on the docs, it would be useful to mention somewhere on https://docs.datomic.com/cloud/operation/new-system.html#storage that the stack name of the storage stack is the system name. (I see it's mentioned https://docs.datomic.com/cloud/operation/storage-template.html#stack-name). That was my one snag