This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-08
Channels
- # announcements (5)
- # babashka (46)
- # beginners (206)
- # boot (1)
- # bristol-clojurians (1)
- # calva (9)
- # chlorine-clover (27)
- # cider (1)
- # clara (10)
- # clj-kondo (105)
- # cljsrn (2)
- # clojars (1)
- # clojure (104)
- # clojure-europe (6)
- # clojure-nl (2)
- # clojure-uk (18)
- # clojurescript (44)
- # conjure (10)
- # core-async (34)
- # cursive (28)
- # data-science (6)
- # datomic (14)
- # emacs (44)
- # events (1)
- # figwheel-main (1)
- # fulcro (13)
- # graphql (9)
- # helix (12)
- # kaocha (2)
- # meander (4)
- # off-topic (2)
- # pathom (1)
- # quil (1)
- # re-frame (21)
- # shadow-cljs (49)
- # spacemacs (6)
- # xtdb (8)
Are there any notes on doing backup + restore of a single node that uses rocksdb? Would copying the db-dir and event-log dir be sufficient for a cheap (easy) solution?
Hey @U051V5LLP copying the directories should be fine when the node is powered down. If the node needs to stay running then you can use crux.backup/backup
and friends
Cool, thank you - i'll take a look into that Is there a recommended setup for single node deploy (using sql or single-node kafka for example)?
Mostly concerned with data loss, This is my config at the moment:
(defn rocks-config [data-dir]
{:crux.node/topology '[crux.standalone/topology
crux.kv.rocksdb/kv-store]
:crux.kv/db-dir (str (io/file data-dir "db"))
:crux.standalone/event-log-dir (str (io/file data-dir "eventlog"))
:crux.standalone/event-log-kv-store 'crux.kv.rocksdb/kv
:crux.standalone/event-log-sync? true
:crux.kv/sync? true})
If you're thinking of running postgres or a small kafka setup on the same machine as your single node then I think that's overkill and you probably are better off just using rocks, but I would personally use a managed jdbc backend (via crux-jdbc) or managed kafka of some kind (esp. Confluent Cloud).