This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-02
Channels
- # announcements (1)
- # babashka (4)
- # beginners (39)
- # calva (36)
- # cherry (11)
- # cider (23)
- # clj-on-windows (3)
- # clojure (105)
- # clojure-brasil (1)
- # clojure-chicago (3)
- # clojure-conj (8)
- # clojure-denver (4)
- # clojure-europe (18)
- # clojure-germany (5)
- # clojure-hungary (13)
- # clojure-nl (1)
- # clojure-norway (31)
- # clojure-sweden (9)
- # clojure-uk (2)
- # clojurescript (22)
- # core-async (4)
- # cursive (8)
- # data-science (25)
- # datomic (14)
- # devops (1)
- # emacs (9)
- # events (5)
- # holy-lambda (32)
- # hyperfiddle (26)
- # introduce-yourself (2)
- # kaocha (1)
- # leiningen (11)
- # lsp (17)
- # malli (8)
- # off-topic (84)
- # pedestal (4)
- # polylith (2)
- # re-frame (17)
- # reitit (1)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (8)
- # sql (4)
- # tools-deps (8)
- # transit (5)
- # vim (1)
- # vscode (1)
- # xtdb (45)
The http health check endpoint https://docs.datomic.com/pro/overview/transactor.html#health-check-endpoint seems to no longer work with 1.0.6726, no answer from the port configured with ping-port
@U7PQLLK0S can you share how you are setting ping-port
? In the properties file or at the command line?
But not really a problem, I just changed the k8s readiness probe to do a tcp socket check to the regular datomic client port. Just caused some confusion on upgrading to the new version.
@U7PQLLK0S thanks for the report. I confirmed this is a bug introduced in 1.0.6526 and we'll fix and address for next release.
hello, i'm currently in the process of deploying datomic to k8, would you have some examples in how to setup the k8 resources ?
I’m sorry, I don’t really have any clean or perhaps even recommendable examples to give. We have this kinda weird setup where we provision the cloud infra with Terraform and use Ansible to build the container and deploy it to Kubernetes. But basically we just unzip the datomic-pro zip inside a image based on eclipse-temurin:17-jre
and run it with enough resources.
Perhaps a slightly interesting part is this entrypoint script that takes environment variables and prepares transactor.properties with things that Datomic doesn’t want to read from the environment, or at least didn’t back then
#!/bin/bash
cd /opt/datomic-pro-${DATOMIC_VERSION}
./create_table.sh
sed -e "s/CLOUD_SQL_INTERNAL_IP/${SQL_HOST_IP:-localhost}/" \
-e "s/DATOMIC_DB/${DATOMIC_DB:-evolve-datomic}/" \
-e "s/DATOMIC_PASSWORD/${DATOMIC_PASSWORD:-default}/" \
-e "s/DATOMIC_HOST/${DATOMIC_HOST:-localhost}/" \
./transactor.properties.template > ./transactor.properties
./bin/transactor -Xms${DATOMIC_XMS:-3g} -Xmx${DATOMIC_XMX:-3g} ./transactor.properties
(where create_table.sh
is another script that creates the datomic_kvs
table if it does not exist)@U1QJACBUM it’s still broken in the new version 1.0.6733.
@U1LR4AN75 I am aware. The fix is in our next release we were testing 6733 when this was reported. We'll get it out the door soon 🙂
@U1QJACBUM do you have any ETA for the next release? We’re unable to upgrade now, since we’re required to do some health check 😅 TCP check isn’t working for standby instances, so there doesn’t appear to be a proper workaround now